Rollup of 5 pull requests

[JonathanBrouwer]

Successful merges:

• Guard patterns: lowering to THIR #153828 (Guard patterns: lowering to THIR)
• refactor - moving check_stability check to parse_stability #154015 (refactor - moving check_stability check to parse_stability)
• llvm: Update reliable_f128 configuration for LLVM22 on Sparc #154119 (llvm: Update reliable_f128 configuration for LLVM22 on Sparc)
• vec::Drain::fill: avoid reference to uninitialized memory #154138 (vec::Drain::fill: avoid reference to uninitialized memory)
• test copy_specializes_from_vecdeque: reduce iteration count for Miri #154143 (test copy_specializes_from_vecdeque: reduce iteration count for Miri)

r? @ghost

Create a similar rollup

[JonathanBrouwer]

@bors r+ rollup=never p=5

[rust-bors]

📌 Commit 80faf6f has been approved by JonathanBrouwer

It is now in the queue for this repository.

[rust-bors]

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

[github-actions]

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 ac7f9ec (parent) -> 9e0a42c (this PR)

Test differences

Show 56 test diffs

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

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 9e0a42c7abbe50c2cc618220d098b40c34a55564 --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. dist-aarch64-apple: 2h 4m -> 1h 41m (-18.5%)
2. aarch64-apple: 3h -> 3h 29m (+16.5%)
3. dist-sparcv9-solaris: 1h 40m -> 1h 24m (-15.3%)
4. x86_64-gnu-llvm-21-2: 1h 37m -> 1h 26m (-11.3%)
5. dist-x86_64-apple: 2h 12m -> 1h 59m (-9.6%)
6. dist-x86_64-msvc-alt: 2h 35m -> 2h 49m (+8.9%)
7. x86_64-gnu-llvm-21-3: 2h 7m -> 1h 57m (-8.0%)
8. x86_64-gnu-stable: 2h 29m -> 2h 18m (-7.8%)
9. dist-various-2: 40m 10s -> 37m 18s (-7.1%)
10. arm-android: 1h 39m -> 1h 46m (+7.0%)

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]

Finished benchmarking commit (9e0a42c): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

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

Max RSS (memory usage)

Results (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)	1.8%	[1.7%, 1.8%]	2
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-2.1%	[-3.1%, -1.0%]	2
All ❌✅ (primary)	-	-	0

Cycles

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

Binary size

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

Bootstrap: 485.09s -> 484.809s (-0.06%)
Artifact size: 394.98 MiB -> 396.94 MiB (0.50%)