-
Notifications
You must be signed in to change notification settings - Fork 13.3k
match lowering: Remove the make_target_blocks
hack
#119112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
It was introduced 4 years ago in a1d0266 to improve LLVM optimization time. Measurements today indicate it is no longer needed.
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
… r=<try> match lowering: Remove the `make_target_blocks` hack This hack was introduced 4 years ago in [`a1d0266` (rust-lang#60730)](rust-lang@a1d0266) to improve LLVM optimization time, specifically noticed in the `encoding` benchmark. Measurements today indicate it is no longer needed. r? `@matthewjasper`
Maybe try it locally with rustc-perf to make sure? We only run this benchmark as part of the "stable" benchmarks, not on every PR anymore (since rust-lang/rustc-perf@ce8ad46). |
Oh damn I did not notice that. Will do! |
I measure only a 0.15% regression locally! |
It would be nice to have a rust-perf option to run the stable-only benchmarks, I don't fully trust my local measurements (though for once they seem consistent) |
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (bbc076f): comparison URL. Overall result: no relevant changes - no 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. @bors rollup=never Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. 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: 671.446s -> 672.298s (0.13%) |
@bors r+ |
Thank you! Do you know when the stable benchmarks are run on CI? |
IIRC for each stable release for the perf dashboard. |
☀️ Test successful - checks-actions |
Finished benchmarking commit (f704f3b): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. 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: 671.988s -> 674.398s (0.36%) |
This hack was introduced 4 years ago in
a1d0266
(#60730) to improve LLVM optimization time, specifically noticed in theencoding
benchmark. Measurements today indicate it is no longer needed.r? @matthewjasper