Conversation
|
These commits modify compiler targets. |
This comment has been minimized.
This comment has been minimized.
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
Update to LLVM 18 Blocked on rust-lang#116672. r? `@ghost`
|
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (b10e375): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Bootstrap: 665.924s -> 629.581s (-5.46%) |
|
Regarding runtime benchmarks, looks like some improvements were made to hashbrown's bitmask: I tried finding codegen differences using |
|
This may be a bit offtopic, but @nikic -- any chance https://reviews.llvm.org/D159075 gets into LLVM18? It's the last patch in the series and shame to see it get lost :(. |
|
dist-390x-linux fails with: |
|
This looks like an issue in the compiler-builtins build script, which unconditionally adds files for 80-bit long double builtins in https://github.com/rust-lang/compiler-builtins/blob/ab849edf5c9e66ad2c9194f83b023847bd6dbe6d/build.rs#L289 We should only be doing that on x86 -- or maybe not at all? Does rust even support 80-bit floats? |
|
Submitted rust-lang/compiler-builtins#568 to fix this. |
|
rust-lang/compiler-builtins#564 is also needed for aarch64. |
|
The codegen test update is now part of #120265. |
|
test-various fails wasm32-unknown-unknown run-make with failures like these: Key part: |
|
The wasm issue was introduced by llvm/llvm-project#78658. |
|
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (eaff1af): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Bootstrap: 664.861s -> 631.785s (-4.97%) |
|
Definitely more wins than losses :) @rustbot label: +perf-regression-triaged |
This bisects to rust-lang/rust#120055. Running tests/exhaustive.rs (target/release/deps/exhaustive-e2f6c3a78f65e6a2) running 1 test thread 'test' has overflowed its stack fatal runtime error: stack overflow error: test failed, to rerun pass `--test exhaustive` Caused by: process didn't exit successfully: `target/release/deps/exhaustive-e2f6c3a78f65e6a2` (signal: 6, SIGABRT: process abort signal)
Update tests for changes in latest nightly There were two changes that has caused nightly tests to start failing: * LLVM was updated, and that caused a change in the expected data layout for the target. (rust-lang/rust#120055 update to LLVM 18) * rust-lang/rust#121049 Do not point at `#[allow(_)]` as the reason for compat lint triggering. The test was looking for the `unused_variables` note, which is no longer printed.
LLVM 18 final is planned to be released on Mar 5th. Rust 1.78 is planned to be released on May 2nd.
Tested images: dist-x86_64-linux, dist-s390x-linux, dist-aarch64-linux, dist-riscv64-linux, dist-loongarch64-linux, dist-x86_64-freebsd, dist-x86_64-illumos, dist-x86_64-musl, x86_64-linux-integration, test-various, armhf-gnu, i686-msvc, x86_64-msvc, i686-mingw, x86_64-mingw, x86_64-apple-1, x86_64-apple-2, dist-aarch64-apple
r? @ghost