Conversation
we should not get the certainty from the current result of the provisional cache entry
…pre-fallback where we equate hidden types but do not report errors
…ve the assert in favor over a comment, and change to & for &mut
* Adds armv7a-none-eabihf (rust-lang#146522) * Adds armv8r-none-eabihf (rust-lang#146520) * Drops armeb*-none-* (rust-lang#146523)
Not all ARMv7-A CPUs have a double-precision FPU. So adjust the CFLAGS from `+vfpv3` (which assumes 32 double-precision registers) to `+fp` (which only assumes 16 double-precision registers).
These two steps are currently the most verbose steps in a dist-linux build, which makes it harder to find more interesting parts. Hide them in a group like most things.
…inimizations. Update comment and test.
Enable `u64` limbs in `core::num::bignum` Since `u128` is stable now, I guess, we can safely add this, not sure if this requires tests or anything cc rust-lang#137887
constify basic Clone impls
Do two passes of `handle_opaque_type_uses_next` Fixes rust-lang/trait-system-refactor-initiative#240 Also did a little bit of cleanup, can squash the commits if decided. r? lcnr
fix 2 search graph bugs wooooooooops, i should really run the fuzzer even when not changing the structure of the search graph as a whole :3 fixes the `ml-kem` ICE in the next-solver crater run r? ````@BoxyUwU````
…etrochenkov `proc_macro` cleanups (3/N) Followup to rust-lang#147386, which removed the old `Decode` trait. Can be reviewed commit by commit.
…147542, r=jackh726 Suppress unused_parens for labeled break Fixes rust-lang#147542
…ets, r=Mark-Simulacrum Adjust the Arm targets in CI to reflect latest changes * Adds build of `armv7a-none-eabihf` (rust-lang#146522) * Adds build of `armv8r-none-eabihf` (rust-lang#146520) * Drops build of `armeb*-none-*` (rust-lang#146523) I wasn't sure why `armv7a-none-eabihf` was missing from the build-manifest program, but `armv8r-none-eabihf` was there, as they were both Tier 3 targets up until very recently. So, I added it, but that might be wrong.
GVN: Invalidate derefs at loop headers Fix a miscompiled case I found when re-reviewing rust-lang#132527. r? cjgillot r? oli-obk
…ottmcm Avoid redundant UB check in RangeFrom slice indexing I noticed this while picking through the IR we generate for rust-lang#134938. I think we just forgot to apply this trick to `RangeFrom`?
…thar Hide vendoring and copyright in GHA group These two steps are currently the most verbose steps in a dist-linux build, which makes it harder to find more interesting parts. Hide them in a group like most things. For example, see https://github.com/rust-lang/rust/actions/runs/18462295959/job/52596384752
|
☀️ Test successful - checks-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 2f7620a (parent) -> e100792 (this PR) Test differencesShow 100 test diffsStage 1
Stage 2
Additionally, 86 doctest diffs were found. These are ignored, as they are noisy. Job group index
Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard e100792918c8bd9e0cb830f96fc9b171e8892fa1 --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
📌 Perf builds for each rolled up PR:
previous master: 2f7620a5cc In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
|
Finished benchmarking commit (e100792): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowOur benchmarks found a performance regression caused by this PR. Next Steps:
@rustbot label: +perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 2.5%, secondary -3.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -0.1%, secondary -0.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 475.635s -> 473.51s (-0.45%) |
|
The perf change is from #147620 (comment) |
Rollup of 12 pull requests Successful merges: - rust-lang#146277 (Enable `u64` limbs in `core::num::bignum`) - rust-lang#146976 (constify basic Clone impls) - rust-lang#147249 (Do two passes of `handle_opaque_type_uses_next`) - rust-lang#147266 (fix 2 search graph bugs) - rust-lang#147497 (`proc_macro` cleanups (3/N)) - rust-lang#147546 (Suppress unused_parens for labeled break) - rust-lang#147548 (Fix ICE for never pattern as closure parameters) - rust-lang#147594 (std: implement `pal::os::exit` for VEXos) - rust-lang#147596 (Adjust the Arm targets in CI to reflect latest changes) - rust-lang#147607 (GVN: Invalidate derefs at loop headers) - rust-lang#147620 (Avoid redundant UB check in RangeFrom slice indexing) - rust-lang#147647 (Hide vendoring and copyright in GHA group) r? `@ghost` `@rustbot` modify labels: rollup
Successful merges:
u64limbs incore::num::bignum#146277 (Enableu64limbs incore::num::bignum)handle_opaque_type_uses_next#147249 (Do two passes ofhandle_opaque_type_uses_next)proc_macrocleanups (3/N) #147497 (proc_macrocleanups (3/N))pal::os::exitfor VEXos #147594 (std: implementpal::os::exitfor VEXos)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup