Rollup of 22 pull requests#154958
Conversation
…er of overly generic free const items
…ax_by A recent regression swapped the argument order passed to the compare closure in min_by, max_by and minmax_by (compare(&v2, &v1) instead of compare(&v1, &v2)). This was fixed, but no regression test was added. Add tests that record the arguments the compare closure receives and assert they match (v1, v2) — the documented contract.
abort_internal() is used in panics; if it calls core::intrinsics::abort(), the process triggers an invalid op code (on x86_64), which is a much harder "abort" than a user-controlled exit via a panic. Most other OSes don't use core::intrinsics::abort() here, but either libc::abort(), or a native OS abort/exit API.
Same as 147495, just keeping it up-to-date.
Since a1feab1 ("Use libm for acosh and asinh"), the standard library may link these functions to get a more accurate approximation; however, some targets do not have the needed symbols available. Add them to the compiler-builtins export list to make sure the fallback is usable.
This comment has been minimized.
This comment has been minimized.
Rollup of 22 pull requests try-job: dist-various-1 try-job: test-various try-job: x86_64-gnu-aux try-job: x86_64-gnu-llvm-21-3 try-job: x86_64-msvc-1 try-job: aarch64-apple try-job: x86_64-mingw-1
This comment has been minimized.
This comment has been minimized.
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 ad4b935 (parent) -> c756124 (this PR) Test differencesShow 2207 test diffsStage 1
Stage 2
Additionally, 2170 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 c756124775121dea0e640652c5ee3c89e3dd0eb4 --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: ad4b935400 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
|
Finished benchmarking commit (c756124): comparison URL. Overall result: ❌✅ regressions and improvements - no action needed@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 1.5%, secondary 0.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -2.6%, secondary 3.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -0.0%, secondary -0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 488.293s -> 494.654s (1.30%) |
Successful merges:
TaggedQueryKey::def_kind#153999 (RemoveTaggedQueryKey::def_kind)Cycleto a newprocess_cyclefunction #154146 (Split out the creation ofCycleto a newprocess_cyclefunction)tests/ui/issuesto appropriate directories #154506 (Migrate some tests fromtests/ui/issuesto appropriate directories)Step for NonZero<u*>#154825 (constifyStep for NonZero<u*>)impl_trait_in_assoc_type#146514)cfg(target_arch)on scalable intrinsics #154950 (library: nocfg(target_arch)on scalable intrinsics)r? @ghost
Create a similar rollup