Skip to content

Rollup of 3 pull requests#156257

Merged
rust-bors[bot] merged 52 commits intorust-lang:mainfrom
JonathanBrouwer:rollup-WThya34
May 7, 2026
Merged

Rollup of 3 pull requests#156257
rust-bors[bot] merged 52 commits intorust-lang:mainfrom
JonathanBrouwer:rollup-WThya34

Conversation

@JonathanBrouwer
Copy link
Copy Markdown
Contributor

Successful merges:

r? @ghost

Create a similar rollup

xtqqczze and others added 30 commits January 31, 2026 23:52
seems unnecessary to use `macos-15-large` just for x86_64 support
provide a reminder on the signedness of a failed `assert_simm_bits`
Most of the changes in the JSON were merged earlier in the SVE
intrinsics PR
…nsic-test-fixes

Fix lane-swapping on pairwise big endian Neon intrinsic
…nsics

hexagon: Add scalar DSP intrinsics
…eon-tests

Add more manual aarch64 load/store intrinsic tests
Implement AVX512-VP2INTERSECT intrinsics
This updates the rust-version file to e22c616.
This change migrates a subset of LSX/LASX intrinsics to the portable
`intrinsics::simd` interface.

Only straightforward mappings are converted in this patch. Intrinsics
that require more complex transformations or currently result in
suboptimal code generation are intentionally left unchanged and will be
migrated incrementally in follow-up patches.
loongarch: Use `intrinsics::simd` for selected LSX/LASX intrinsics
these functions write to a raw pointer, and so are clearly unsafe to use
Amanieu and others added 11 commits May 6, 2026 09:11
…, r=folkertdev

stdarch subtree update

Subtree update of `stdarch` to rust-lang/stdarch@6b174ad.

Created using https://github.com/rust-lang/josh-sync.

r? @ghost
Don't return dummy MacroData in `get_macro`

I was experimenting with tool attributes and ast manipulation, and wasted some time figuring out that this was happening. AFAIK all users of `get_macro` are expecting an actual macro (and none were reading the dummy MacroData) so there should be no change in behavior.
…cation, r=wesleywiser

tests/ui: allow spaces in hashbrown src normalization

If one's home directory contains a space, the default location for the hashbrown source location also contains a space, and so the UI test normalization in issue-21763 fails to normalize as expected.

While this new regex does not handle all valid paths, such as those beginning with `\\?\` or `\\name\`, this handles most absolute UNIX and Windows paths. Relative paths don't seem to be applicable.
@rust-bors rust-bors Bot added the rollup A PR which is a rollup label May 6, 2026
@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. 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. labels May 6, 2026
@JonathanBrouwer
Copy link
Copy Markdown
Contributor Author

@bors r+ rollup=never p=5

@rust-bors
Copy link
Copy Markdown
Contributor

rust-bors Bot commented May 6, 2026

📌 Commit 2744cb7 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 May 6, 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 May 7, 2026
@rust-bors
Copy link
Copy Markdown
Contributor

rust-bors Bot commented May 7, 2026

☀️ Test successful - CI
Approved by: JonathanBrouwer
Duration: 3h 10m 27s
Pushing a4069f5 to main...

@rust-bors rust-bors Bot merged commit a4069f5 into rust-lang:main May 7, 2026
12 checks passed
@rustbot rustbot added this to the 1.97.0 milestone May 7, 2026
@rust-timer
Copy link
Copy Markdown
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#156151 Don't return dummy MacroData in get_macro 0d58947f3e8ca784e69c03e394d607317adc1e1e (link)
#156211 tests/ui: allow spaces in hashbrown src normalization ab083437bcfd5cf0ec0d5d25baa1bddae10c574e (link)
#156251 stdarch subtree update fd9aeadb90dcd9c56938aeb6aa8cc699c81b254a (link)

previous master: 365c0e1d7a

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 7, 2026

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 365c0e1 (parent) -> a4069f5 (this PR)

Test differences

Show 4 test diffs

Stage 1

  • [ui] tests/ui/cfg/reserved-macro-names-rename.rs: [missing] -> pass (J1)

Stage 2

  • [ui] tests/ui/cfg/reserved-macro-names-rename.rs: [missing] -> pass (J0)

Additionally, 2 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 a4069f5bd099e4cf94c2313a47d864f6479ee304 --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. x86_64-gnu-llvm-21-2: 1h 41m -> 1h 13m (-27.4%)
  2. x86_64-gnu-distcheck: 2h 18m -> 1h 47m (-22.3%)
  3. dist-powerpc64le-linux-musl: 1h 18m -> 1h 36m (+21.9%)
  4. x86_64-gnu-llvm-22-1: 1h 18m -> 1h 3m (-19.5%)
  5. dist-ohos-x86_64: 1h 17m -> 1h 3m (-17.9%)
  6. dist-x86_64-illumos: 1h 26m -> 1h 41m (+17.7%)
  7. pr-check-1: 34m 27s -> 28m 38s (-16.9%)
  8. x86_64-gnu-llvm-21-1: 1h 19m -> 1h 6m (-16.7%)
  9. i686-gnu-2: 1h 42m -> 1h 26m (-15.3%)
  10. aarch64-gnu-debug: 1h 18m -> 1h 6m (-15.1%)
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 (a4069f5): 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.3% [-0.4%, -0.3%] 2
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (primary 1.4%, secondary -0.3%)

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

mean range count
Regressions ❌
(primary)
1.4% [0.9%, 1.8%] 2
Regressions ❌
(secondary)
2.8% [0.7%, 7.1%] 5
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-3.5% [-7.0%, -1.5%] 5
All ❌✅ (primary) 1.4% [0.9%, 1.8%] 2

Cycles

Results (primary -2.4%, secondary -0.2%)

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.0% [5.0%, 5.0%] 1
Improvements ✅
(primary)
-2.4% [-2.4%, -2.4%] 1
Improvements ✅
(secondary)
-0.8% [-2.0%, -0.5%] 8
All ❌✅ (primary) -2.4% [-2.4%, -2.4%] 1

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%] 4
Regressions ❌
(secondary)
0.0% [0.0%, 0.0%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.0% [0.0%, 0.0%] 4

Bootstrap: 501.88s -> 500.816s (-0.21%)
Artifact size: 395.21 MiB -> 395.23 MiB (0.01%)

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

Labels

merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup 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.