Rollup of 4 pull requests - #161822
Conversation
…codes UEFI status codes are usize-wide with the high bit set for errors (e.g. DEVICE_ERROR is 0x8000000000000007 on 64-bit). the previous `as i32` cast silently dropped the upper bits, losing all error information. stripping the error high bit to extract the error number and negating it, so errors (negative) are distinguishable from success/warning codes (non-negative).
Alloc `String::retain` optimization Hi again! This uses the exact same algorithm as my other PR: rust-lang#149784 Technically it should improve performance for `String::retain` too, But let's see what bors thinks.
std::process: fix UEFI ExitStatus::code() silent truncation of error … …codes UEFI status codes are usize-wide with the high bit set for errors (e.g. DEVICE_ERROR is 0x8000000000000007 on 64-bit). the previous `as i32` cast silently dropped the upper bits, losing all error information. stripping the error high bit to extract the error number and negating it, so errors (negative) are distinguishable from success/warning codes (non-negative).
Deny #[inline] on EII declarations
…jorn3 Rename dlltool helper function It doesn't check for MinGW toolchain (`windows-gnu` or `windows-gnullvm`), but `windows-gnu` only. All the callsites use that helper to decide whether dlltool should be used. r? @bjorn3
This comment has been minimized.
This comment has been minimized.
Rollup of 4 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-1 try-job: aarch64-apple-2 try-job: x86_64-mingw-1 try-job: i686-msvc-1 try-job: i686-msvc-2
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 c241221 (parent) -> 3b8ee6c (this PR) Test differencesShow 147 test diffs147 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 3b8ee6c0ca55afb08e2e130003227a3195394425 --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 |
|
Finished benchmarking commit (3b8ee6c): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis perf run didn't have relevant results for this metric. Max RSS (memory usage)Results (secondary -2.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesThis perf run didn't have relevant results for this metric. Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 474.908s -> 473.778s (-0.24%) |
|
📌 Perf builds for each rolled up PR:
parent commit: c24122146b In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Successful merges:
String::retainoptimization #150067 (AllocString::retainoptimization)r? @ghost
Create a similar rollup