Skip to content

Rollup of 14 pull requests#154008

Merged
rust-bors[bot] merged 62 commits intorust-lang:mainfrom
JonathanBrouwer:rollup-tfGnRi2
Mar 17, 2026
Merged

Rollup of 14 pull requests#154008
rust-bors[bot] merged 62 commits intorust-lang:mainfrom
JonathanBrouwer:rollup-tfGnRi2

Conversation

@JonathanBrouwer
Copy link
Contributor

Successful merges:

r? @ghost

Create a similar rollup

sayantn and others added 30 commits March 2, 2026 00:32
Add immediate-mode AMX intrinsics
Fix LLVM intrinsic signatures for AVX-VNNI
…atures

remove use of `wasm_target_feature` on wasm target arch
Correct const-stability attribute for avx512bw intrinsics
This updates the rust-version file to eda4fc7.
…at-min-max"

This reverts commit 6a8a764262df5e65c06bc5d9180046a636a53ce9, reversing
changes made to a37563b5f8cec0c873864b786c33d00386189916.
Revert "Merge pull request rust-lang#1871 from folkertdev/aarch64-float-min-max"
s390x: use llvm intrinsics instead of simd_fmin/fmax
…duce-min-max

aarch64: use `simd_reduce_{min, max}` on integers
ci is showing a lot of warnings (72) right now. apparently
actions/checkout@v4 uses Node.js 20, and all github actions are
scheduled to be force opted-in to Node.js 24 on 2026-06-02.
I don't anticipate bumping the checkout action to v6 / Node.js 24
to cause any issues (Node.js 24 drops support for ARM32 and macOS
versions <= 13.4, but this shouldn't matter because we use Docker
to test in those environments, not github runners natively) but if
it does cause issues it's probably better to find out now rather
than by surprise 3 months from now... :)
@rustbot rustbot added A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure 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. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver) labels Mar 17, 2026
@JonathanBrouwer
Copy link
Contributor Author

@bors r+ rollup=never p=5

@rust-bors
Copy link
Contributor

rust-bors bot commented Mar 17, 2026

📌 Commit 880d85f has been approved by JonathanBrouwer

It is now in the queue for this repository.

@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 Mar 17, 2026
@rust-bors rust-bors bot mentioned this pull request Mar 17, 2026
@rust-bors

This comment has been minimized.

@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 Mar 17, 2026
@rust-bors
Copy link
Contributor

rust-bors bot commented Mar 17, 2026

☀️ Test successful - CI
Approved by: JonathanBrouwer
Duration: 3h 19m 6s
Pushing 85e19b8 to main...

@rust-bors rust-bors bot merged commit 85e19b8 into rust-lang:main Mar 17, 2026
12 checks passed
@rustbot rustbot added this to the 1.96.0 milestone Mar 17, 2026
@github-actions
Copy link
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 b711f95 (parent) -> 85e19b8 (this PR)

Test differences

Show 676 test diffs

Stage 1

  • [ui] tests/ui/coercion/no-implicit-box-to-ref-coercion.rs: [missing] -> pass (J0)
  • [ui] tests/ui/cross-crate/cross-crate-macro-backtrace.rs: [missing] -> pass (J0)
  • [ui] tests/ui/cross/cross-borrow-trait.rs: pass -> [missing] (J0)
  • [ui] tests/ui/cross/cross-crate-macro-backtrace/main.rs: pass -> [missing] (J0)
  • [ui] tests/ui/cross/cross-file-errors/main.rs: pass -> [missing] (J0)
  • [ui] tests/ui/cross/cross-file-errors/underscore.rs: ignore (ignored used by another main test file ((used by ./main.rs))) -> [missing] (J0)
  • [ui] tests/ui/cross/cross-fn-cache-hole.rs: pass -> [missing] (J0)
  • [ui] tests/ui/float/classify-runtime-const.rs#ctfe: pass -> ignore (ignored when the LLVM version 21.1.2 is older than 22.0.0) (J0)
  • [ui] tests/ui/float/classify-runtime-const.rs#noopt: pass -> ignore (ignored when the LLVM version 21.1.2 is older than 22.0.0) (J0)
  • [ui] tests/ui/float/classify-runtime-const.rs#opt: pass -> ignore (ignored when the LLVM version 21.1.2 is older than 22.0.0) (J0)
  • [ui] tests/ui/macros/cross-file-errors.rs: [missing] -> pass (J0)
  • [ui] tests/ui/macros/underscore.rs: [missing] -> ignore (ignored used by another main test file ((used by ./main.rs))) (J0)
  • [ui] tests/ui/resolve/pub-in-path-153848.rs: [missing] -> pass (J0)
  • [ui] tests/ui/traits/cross-fn-cache-hole.rs: [missing] -> pass (J0)

Stage 2

  • [ui] tests/ui/coercion/no-implicit-box-to-ref-coercion.rs: [missing] -> pass (J1)
  • [ui] tests/ui/cross-crate/cross-crate-macro-backtrace.rs: [missing] -> pass (J1)
  • [ui] tests/ui/cross/cross-borrow-trait.rs: pass -> [missing] (J1)
  • [ui] tests/ui/cross/cross-crate-macro-backtrace/main.rs: pass -> [missing] (J1)
  • [ui] tests/ui/cross/cross-file-errors/main.rs: pass -> [missing] (J1)
  • [ui] tests/ui/cross/cross-file-errors/underscore.rs: ignore (ignored used by another main test file ((used by ./main.rs))) -> [missing] (J1)
  • [ui] tests/ui/cross/cross-fn-cache-hole.rs: pass -> [missing] (J1)
  • [ui] tests/ui/macros/cross-file-errors.rs: [missing] -> pass (J1)
  • [ui] tests/ui/macros/underscore.rs: [missing] -> ignore (ignored used by another main test file ((used by ./main.rs))) (J1)
  • [ui] tests/ui/resolve/pub-in-path-153848.rs: [missing] -> pass (J1)
  • [ui] tests/ui/traits/cross-fn-cache-hole.rs: [missing] -> pass (J1)
  • [ui] tests/ui/float/classify-runtime-const.rs#ctfe: pass -> ignore (ignored when the LLVM version 21.1.2 is older than 22.0.0) (J2)
  • [ui] tests/ui/float/classify-runtime-const.rs#noopt: pass -> ignore (ignored when the LLVM version 21.1.2 is older than 22.0.0) (J2)
  • [ui] tests/ui/float/classify-runtime-const.rs#opt: pass -> ignore (ignored when the LLVM version 21.1.2 is older than 22.0.0) (J2)

Additionally, 648 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 85e19b8ce869aaef0d5389a050ddee7b258b8029 --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. pr-check-1: 28m 14s -> 33m 12s (+17.6%)
  2. dist-apple-various: 1h 29m -> 1h 42m (+15.1%)
  3. x86_64-rust-for-linux: 49m 14s -> 56m 38s (+15.0%)
  4. aarch64-apple: 2h 56m -> 2h 31m (-14.2%)
  5. dist-ohos-x86_64: 1h 10m -> 1h 17m (+10.0%)
  6. dist-x86_64-netbsd: 1h 23m -> 1h 30m (+8.6%)
  7. x86_64-gnu-llvm-21: 1h 11m -> 1h 17m (+8.5%)
  8. dist-aarch64-llvm-mingw: 1h 34m -> 1h 41m (+8.0%)
  9. dist-ohos-armv7: 1h 7m -> 1h 13m (+7.7%)
  10. x86_64-gnu-distcheck: 2h 19m -> 2h 9m (-7.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
Collaborator

Finished benchmarking commit (85e19b8): comparison URL.

Overall result: ❌✅ regressions and 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.2% [0.2%, 0.2%] 1
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-0.1% [-0.1%, -0.1%] 2
All ❌✅ (primary) 0.2% [0.2%, 0.2%] 1

Max RSS (memory usage)

Results (primary -1.6%, 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)
1.7% [1.3%, 2.3%] 3
Improvements ✅
(primary)
-1.6% [-2.9%, -0.6%] 7
Improvements ✅
(secondary)
-2.3% [-4.1%, -1.1%] 16
All ❌✅ (primary) -1.6% [-2.9%, -0.6%] 7

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

Results (primary 0.0%, secondary 0.0%)

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

mean range count
Regressions ❌
(primary)
0.0% [0.0%, 0.0%] 8
Regressions ❌
(secondary)
0.0% [0.0%, 0.0%] 2
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.0% [0.0%, 0.0%] 8

Bootstrap: 481.409s -> 480.745s (-0.14%)
Artifact size: 394.91 MiB -> 396.86 MiB (0.49%)

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

Labels

A-attributes Area: Attributes (`#[…]`, `#![…]`) A-CI Area: Our Github Actions CI A-compiletest Area: The compiletest test runner A-query-system Area: The rustc query system (https://rustc-dev-guide.rust-lang.org/query.html) A-rustc-dev-guide Area: rustc-dev-guide A-testsuite Area: The testsuite used to check the correctness of rustc merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure 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. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver)

Projects

None yet

Development

Successfully merging this pull request may close these issues.