Skip to content

Rollup of 9 pull requests - #163465

Merged
rust-bors[bot] merged 29 commits into
rust-lang:mainfrom
tgross35:rollup-VJQsybH
Sep 29, 2026
Merged

rust-bors[bot] merged 29 commits into
rust-lang:mainfrom
tgross35:rollup-VJQsybH

Conversation

@tgross35

Copy link
Copy Markdown
Member

Successful merges:

r? @ghost

Create a similar rollup

tgross35 and others added 29 commits August 25, 2026 22:39
`funnel_shl` and `funnel_shr` have been around for close to a year, the
unchecked versions for a number of months. These are reasonably small
and uncontroversial, and it can be tricky to get similar performance
with a fallback; stabilize them here.

Newly stable API:

    impl {u8, u16, u32, u64, u128, usize} {
        pub const fn funnel_shl(self, right: Self, shift: u32) -> Self;
        pub const fn funnel_shr(self, right: Self, shift: u32) -> Self;

        pub const unsafe fn unchecked_funnel_shl(self, right: Self, shift: u32) -> Self;
        pub const unsafe fn unchecked_funnel_shr(self, right: Self, shift: u32) -> Self;
    }

The tracking issue also mentions a `wrapping_` version but it has not
been implemented.

Tracking issue: RUST-145686
For production use, we should only link in the ubsan_minimal runtime,
instead of the complete ubsan runtime. This adds support for both
cfi-recover and cfi-diag to use the minimal runtime when
`-Zsanitizer-cfi-minimal-runtime` is specified.

This also includes tests, to ensure the flag can only be used if either
cfi-recover or cfi-diag is enabled, it doesn't disrupt the original
behavior, and links in the correct runtime when specified.

Co-Authored-By: Bastian Kersting <bkersting@google.com>
Co-Authored-By: Bastian Kersting <bkersting@google.com>
Only check `SanitizerCfiMinimalRuntimeRequiresCfiRecoverOrDiag` if CFI
is actually enabled.

Use `is_sanitizer_cfi_minimal_runtime_enabled()` helper within
`link.rs`.
…r=nia-e

Stabilize `funnel_shifts` (including `const`)

`funnel_shl` and `funnel_shr` have been around for close to a year, the unchecked versions for a number of months. These are reasonably small and uncontroversial, and it can be tricky to get similar performance with a fallback; stabilize them here.

Newly stable API:

```rust
impl {u8, u16, u32, u64, u128, usize} {
    pub const fn funnel_shl(self, right: Self, shift: u32) -> Self;
    pub const fn funnel_shr(self, right: Self, shift: u32) -> Self;

    pub const unsafe fn unchecked_funnel_shl(self, right: Self, shift: u32) -> Self;
    pub const unsafe fn unchecked_funnel_shr(self, right: Self, shift: u32) -> Self;
}
```

The tracking issue also mentions a `wrapping_` version but it has not been implemented.

Closes: rust-lang#145686 (tracking issue, wrapping versions will need a new issue)
…=rcvalle

Add support for -Zsanitizer-cfi-minimal-runtime

For production use, we should only link in the ubsan_minimal runtime,
instead of the complete ubsan runtime. This adds support for both
cfi-recover and cfi-diag to use the minimal runtime when
`-Zsanitizer-cfi-minimal-runtime` is specified.

This also includes tests, to ensure the flag can only be used if either
cfi-recover or cfi-diag is enabled, it doesn't disrupt the original
behavior, and links in the correct runtime when specified.

cc @1c3t3a

?r rcvalle
…ed-attribute-documentation, r=clarfonthey

add `automatically_derived` attribute documentation

Documents the `automatically_derived` built-in attribute in `core` via `#[doc(attribute = "automatically_derived")]`

Part of rust-lang#157604
…r=petrochenkov

do not complain about unstable target features on nightly

This was brought up in rust-lang#162235 (comment): we currently print a warning on nightly saying that using an unstable target feature will become a hard error. That's a mistake.

We could either remove the part of the warning that talks about it becoming a hard error, or we could just hide the warning entirely for unstable features on nighty. I went for the latter -- nightly is meant for experimentation with those features so having un-silenceable warnings is not great.

Cc @workingjubilee
… r=jieyouxu

Add `stable_rustc` helper in `run-make-support`

To help with rust-lang#162848 and https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/Testing.20stable.20vs.20nightly.20behavior.20in.20UI.20tests/with/626329887.

For rust-lang#162848, I need to avoid passing `-Zthreads` when the compiler is supposed to act like `stable`. This refactoring makes that simpler; I will only add that flag to `Rustc::new` and not `Rustc::stable`.

r? jieyouxu
…ata, r=petrochenkov

Allow using different index types when reading and writing to tables

Make tables of metadata two-sided: one can write with one index type and read with another, as long as both those types are indexes. That will be used in rust-lang#163321 when we will have `LocalDefIndex` or similar type.

r? @petrochenkov
…, r=hanna-kruppe

Stabilize vec_try_remove

Closes rust-lang#146954 , which is has [completed its FCP with disposition to merge](rust-lang#146954 (comment)).

Hello, this is my first contribution to Rust! I was programming for fun this weekend and I was surprised that this wasn't stabilized, so I thought I would try to contribute.

Disclosure: I am making this PR in my capacity as a Canonical employee.

No LLMs were harmed in the making of this pull request.
@rustbot rustbot added the A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. label Sep 29, 2026
@tgross35

Copy link
Copy Markdown
Member Author

@bors r+ rollup=never p=5

@rust-bors

rust-bors Bot commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

📌 Commit a8ead4a has been tentatively approved by tgross35

It will be put into the queue for this repository once PR CI succeeds.

@rust-bors rust-bors Bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Sep 29, 2026
@jhpratt

jhpratt commented Sep 29, 2026

Copy link
Copy Markdown
Member

@bors force

@rust-bors

rust-bors Bot commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

Unknown command "force". Run @bors help or go to https://bors.rust-lang.org/help to see available commands.

@jhpratt

jhpratt commented Sep 29, 2026

Copy link
Copy Markdown
Member

@bors r=tgross35 force

@rust-bors

rust-bors Bot commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

📌 Commit a8ead4a has been approved by tgross35

It is now in the queue for this repository.

@rust-bors

This comment has been minimized.

@tgross35

Copy link
Copy Markdown
Member Author

Ah forgot about that! Thanks

@jhpratt

jhpratt commented Sep 29, 2026

Copy link
Copy Markdown
Member

All good! I was about to remind you on Zulip

@JonathanBrouwer JonathanBrouwer added the rollup A PR which is a rollup label Sep 29, 2026
@rust-bors rust-bors Bot added merged-by-bors This PR was explicitly merged by bors. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Sep 29, 2026
@rust-bors

rust-bors Bot commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

☀️ Test successful - CI
Approved by: tgross35
Duration: 2h 55m 44s
Pushing 80a4f6c to main...

@github-actions

Copy link
Copy Markdown
Contributor
What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 5d89371 (parent) -> 80a4f6c (this PR)

Test differences

Show 3642 test diffs

Stage 1

  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-diag-mode.rs: pass -> [missing] (J0)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-diag-mode.rs#cfi-diag: [missing] -> pass (J0)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-diag-mode.rs#cfi-diag-minimal-runtime: [missing] -> pass (J0)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-recover-mode.rs: pass -> [missing] (J0)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-recover-mode.rs#cfi-recover: [missing] -> pass (J0)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-recover-mode.rs#cfi-recover-minimal-runtime: [missing] -> pass (J0)
  • [run-make] tests/run-make/sanitizer-cfi-runtime: [missing] -> ignore (ignored on targets without sanitizers support) (J0)
  • [run-make] tests/run-make/unstable-target-feature: [missing] -> pass (J0)
  • [ui (polonius)] tests/ui/const-generics/gca_adts/missing-dependent-features.rs: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/const-generics/gca_adts/none-incomplete.rs: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/const-generics/gca_adts/none.rs: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/feature-gates/feature-gate-gca-adts.rs#with: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/feature-gates/feature-gate-gca-adts.rs#without: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/feature-gates/feature-gate-gca-adts.rs#without_with_min_items: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch-recover.rs#cfi: [missing] -> ignore (ignored on targets without sanitizers support) (J1)
  • [ui (polonius)] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch-recover.rs#cfi-minimal-runtime: [missing] -> ignore (ignored on targets without sanitizers support) (J1)
  • [ui (polonius)] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch.rs#cfi-minimal-runtime: [missing] -> ignore (ignored on targets without sanitizers support) (J1)
  • [ui (polonius)] tests/ui/sanitizer/cfi/minimal-runtime-requires-cfi-recover-or-diag.rs: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/sanitizer/cfi/minimal-runtime-requires-cfi.rs: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/target-feature/unstable-feature.rs: pass -> [missing] (J1)
  • [ui (polonius)] tests/ui/target_modifiers/sanitizer-cfi-minimal-runtime.rs#ok: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/target_modifiers/sanitizer-cfi-minimal-runtime.rs#wrong_flag: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/target_modifiers/sanitizer-cfi-minimal-runtime.rs#wrong_sanitizer: [missing] -> pass (J1)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-diag-mode.rs: ignore (ignored on targets without CFI sanitizer) -> [missing] (J3)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-diag-mode.rs#cfi-diag: [missing] -> ignore (ignored on targets without CFI sanitizer) (J3)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-diag-mode.rs#cfi-diag-minimal-runtime: [missing] -> ignore (ignored on targets without CFI sanitizer) (J3)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-recover-mode.rs: ignore (ignored on targets without CFI sanitizer) -> [missing] (J3)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-recover-mode.rs#cfi-recover: [missing] -> ignore (ignored on targets without CFI sanitizer) (J3)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-recover-mode.rs#cfi-recover-minimal-runtime: [missing] -> ignore (ignored on targets without CFI sanitizer) (J3)
  • [ui] tests/ui/const-generics/gca_adts/missing-dependent-features.rs: [missing] -> pass (J4)
  • [ui] tests/ui/const-generics/gca_adts/none-incomplete.rs: [missing] -> pass (J4)
  • [ui] tests/ui/const-generics/gca_adts/none.rs: [missing] -> pass (J4)
  • [ui] tests/ui/feature-gates/feature-gate-gca-adts.rs#with: [missing] -> pass (J4)
  • [ui] tests/ui/feature-gates/feature-gate-gca-adts.rs#without: [missing] -> pass (J4)
  • [ui] tests/ui/feature-gates/feature-gate-gca-adts.rs#without_with_min_items: [missing] -> pass (J4)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch-recover.rs#cfi: [missing] -> ignore (ignored on targets without sanitizers support) (J4)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch-recover.rs#cfi-minimal-runtime: [missing] -> ignore (ignored on targets without sanitizers support) (J4)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch.rs#cfi-minimal-runtime: [missing] -> ignore (ignored on targets without sanitizers support) (J4)
  • [ui] tests/ui/sanitizer/cfi/minimal-runtime-requires-cfi-recover-or-diag.rs: [missing] -> pass (J4)
  • [ui] tests/ui/sanitizer/cfi/minimal-runtime-requires-cfi.rs: [missing] -> pass (J4)
  • [ui] tests/ui/target-feature/unstable-feature.rs: pass -> [missing] (J4)
  • [ui] tests/ui/target_modifiers/sanitizer-cfi-minimal-runtime.rs#ok: [missing] -> pass (J4)
  • [ui] tests/ui/target_modifiers/sanitizer-cfi-minimal-runtime.rs#wrong_flag: [missing] -> pass (J4)
  • [ui] tests/ui/target_modifiers/sanitizer-cfi-minimal-runtime.rs#wrong_sanitizer: [missing] -> pass (J4)

Stage 2

  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-diag-mode.rs: pass -> [missing] (J2)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-diag-mode.rs#cfi-diag: [missing] -> pass (J2)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-diag-mode.rs#cfi-diag-minimal-runtime: [missing] -> pass (J2)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-recover-mode.rs: pass -> [missing] (J2)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-recover-mode.rs#cfi-recover: [missing] -> pass (J2)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-recover-mode.rs#cfi-recover-minimal-runtime: [missing] -> pass (J2)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-diag-mode.rs: ignore (ignored on targets without CFI sanitizer) -> [missing] (J5)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-diag-mode.rs#cfi-diag: [missing] -> ignore (ignored on targets without CFI sanitizer) (J5)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-diag-mode.rs#cfi-diag-minimal-runtime: [missing] -> ignore (ignored on targets without CFI sanitizer) (J5)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-recover-mode.rs: ignore (ignored on targets without CFI sanitizer) -> [missing] (J5)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-recover-mode.rs#cfi-recover: [missing] -> ignore (ignored on targets without CFI sanitizer) (J5)
  • [codegen] tests/codegen-llvm/sanitizer/cfi/emit-type-checks-recover-mode.rs#cfi-recover-minimal-runtime: [missing] -> ignore (ignored on targets without CFI sanitizer) (J5)
  • [run-make] tests/run-make/sanitizer-cfi-runtime: [missing] -> ignore (ignored on targets without CFI sanitizer) (J5)
  • [ui] tests/ui/const-generics/gca_adts/missing-dependent-features.rs: [missing] -> pass (J6)
  • [ui] tests/ui/const-generics/gca_adts/none-incomplete.rs: [missing] -> pass (J6)
  • [ui] tests/ui/const-generics/gca_adts/none.rs: [missing] -> pass (J6)
  • [ui] tests/ui/feature-gates/feature-gate-gca-adts.rs#with: [missing] -> pass (J6)
  • [ui] tests/ui/feature-gates/feature-gate-gca-adts.rs#without: [missing] -> pass (J6)
  • [ui] tests/ui/feature-gates/feature-gate-gca-adts.rs#without_with_min_items: [missing] -> pass (J6)
  • [ui] tests/ui/target-feature/unstable-feature.rs: pass -> [missing] (J6)
  • [run-make] tests/run-make/sanitizer-cfi-runtime: [missing] -> ignore (gcc backend is marked as ignore) (J7)
  • [run-make] tests/run-make/unstable-target-feature: [missing] -> ignore (gcc backend is marked as ignore) (J7)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch-recover.rs#cfi: [missing] -> ignore (gcc backend is marked as ignore) (J7)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch-recover.rs#cfi-minimal-runtime: [missing] -> ignore (gcc backend is marked as ignore) (J7)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch.rs#cfi-minimal-runtime: [missing] -> ignore (gcc backend is marked as ignore) (J7)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch-recover.rs#cfi: [missing] -> ignore (ignored on targets without CFI sanitizer) (J8)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch-recover.rs#cfi-minimal-runtime: [missing] -> ignore (ignored on targets without CFI sanitizer) (J8)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch.rs#cfi-minimal-runtime: [missing] -> ignore (ignored on targets without CFI sanitizer) (J8)
  • [run-make] tests/run-make/sanitizer-cfi-runtime: [missing] -> ignore (ignored on targets without sanitizers support) (J9)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch-recover.rs#cfi: [missing] -> pass (J10)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch-recover.rs#cfi-minimal-runtime: [missing] -> pass (J10)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch.rs#cfi-minimal-runtime: [missing] -> pass (J10)
  • [run-make] tests/run-make/unstable-target-feature: [missing] -> ignore (only executed when the architecture is x86_64) (J11)
  • [ui] tests/ui/sanitizer/cfi/minimal-runtime-requires-cfi-recover-or-diag.rs: [missing] -> ignore (ignored on targets without CFI sanitizer) (J12)
  • [ui] tests/ui/sanitizer/cfi/minimal-runtime-requires-cfi.rs: [missing] -> ignore (ignored on targets without CFI sanitizer) (J12)
  • [ui] tests/ui/target_modifiers/sanitizer-cfi-minimal-runtime.rs#ok: [missing] -> ignore (ignored on targets without CFI sanitizer) (J12)
  • [ui] tests/ui/target_modifiers/sanitizer-cfi-minimal-runtime.rs#wrong_flag: [missing] -> ignore (ignored on targets without CFI sanitizer) (J12)
  • [ui] tests/ui/target_modifiers/sanitizer-cfi-minimal-runtime.rs#wrong_sanitizer: [missing] -> ignore (ignored on targets without CFI sanitizer) (J12)
  • [ui] tests/ui/sanitizer/cfi/minimal-runtime-requires-cfi-recover-or-diag.rs: [missing] -> pass (J13)
  • [ui] tests/ui/sanitizer/cfi/minimal-runtime-requires-cfi.rs: [missing] -> pass (J13)
  • [ui] tests/ui/target_modifiers/sanitizer-cfi-minimal-runtime.rs#ok: [missing] -> pass (J13)
  • [ui] tests/ui/target_modifiers/sanitizer-cfi-minimal-runtime.rs#wrong_flag: [missing] -> pass (J13)
  • [ui] tests/ui/target_modifiers/sanitizer-cfi-minimal-runtime.rs#wrong_sanitizer: [missing] -> pass (J13)
  • [run-make] tests/run-make/unstable-target-feature: [missing] -> pass (J14)
  • [run-make] tests/run-make/sanitizer-cfi-runtime: [missing] -> pass (J15)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch-recover.rs#cfi: [missing] -> ignore (ignored on targets without sanitizers support) (J16)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch-recover.rs#cfi-minimal-runtime: [missing] -> ignore (ignored on targets without sanitizers support) (J16)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch.rs#cfi-minimal-runtime: [missing] -> ignore (ignored on targets without sanitizers support) (J16)
  • [run-make] tests/run-make/sanitizer-cfi-runtime: [missing] -> ignore (only executed when the operating system is linux) (J17)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch-recover.rs#cfi: [missing] -> ignore (only executed when the operating system is linux) (J17)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch-recover.rs#cfi-minimal-runtime: [missing] -> ignore (only executed when the operating system is linux) (J17)
  • [ui] tests/ui/sanitizer/cfi/fn-ptr-type-mismatch.rs#cfi-minimal-runtime: [missing] -> ignore (only executed when the operating system is linux) (J17)

Additionally, 3546 doctest diffs were found. These are ignored, as they are noisy.

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 80a4f6cdbdc30afa1f27c830386361d22b161286 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. test-x86_64-gnu-gcc-core-tests: 10m 29s -> 17m 34s (+67.6%)
  2. test-i686-gnu-nopt-1: 1h 40m -> 2h 21m (+40.9%)
  3. test-x86_64-gnu-distcheck: 1h 34m -> 2h 11m (+39.6%)
  4. test-x86_64-gnu-miri: 1h 21m -> 49m 40s (-39.4%)
  5. test-x86_64-gnu-aux: 1h 32m -> 2h 7m (+38.5%)
  6. test-armhf-gnu: 1h 10m -> 1h 37m (+37.3%)
  7. dist-ohos-armv7: 1h 21m -> 51m 19s (-36.9%)
  8. test-x86_64-mingw-1: 3h 1m -> 1h 54m (-36.7%)
  9. test-x86_64-msvc-ext2: 1h 23m -> 1h 53m (+36.5%)
  10. test-x86_64-gnu-stdlib-semver-check: 11m 5s -> 15m 1s (+35.5%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (80a4f6c): comparison URL.

Overall result: ✅ improvements - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-0.4% [-0.4%, -0.4%] 1
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (primary -1.7%, secondary 1.6%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
5.5% [5.5%, 5.5%] 1
Improvements ✅
(primary)
-1.7% [-2.1%, -1.2%] 2
Improvements ✅
(secondary)
-2.2% [-2.2%, -2.2%] 1
All ❌✅ (primary) -1.7% [-2.1%, -1.2%] 2

Cycles

Results (secondary 4.8%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
6.8% [2.1%, 16.0%] 3
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-1.4% [-1.4%, -1.4%] 1
All ❌✅ (primary) - - 0

Binary size

This perf run didn't have relevant results for this metric.

Bootstrap: 489.535s -> 490.592s (0.22%)
Artifact size: 406.43 MiB -> 406.37 MiB (-0.02%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-run-make Area: port run-make Makefiles to rmake.rs A-rustc-dev-guide Area: rustc-dev-guide merged-by-bors This PR was explicitly merged by bors. PG-exploit-mitigations Project group: Exploit mitigations rollup A PR which is a rollup T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-clippy Relevant to the Clippy team. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.