-
Notifications
You must be signed in to change notification settings - Fork 13.3k
[DO NOT MERGE] Experimentally force non-leaf frame pointers #115521
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
base: master
Are you sure you want to change the base?
[DO NOT MERGE] Experimentally force non-leaf frame pointers #115521
Conversation
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit cbbed36 with merge d346bd31885b2a741517e772e9ac19eeecc088b5... |
This comment has been minimized.
This comment has been minimized.
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (d346bd31885b2a741517e772e9ac19eeecc088b5): 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: 628.382s -> 631.014s (0.42%) |
Much better, but still a pretty hard sell. |
cbbed36
to
2455c14
Compare
The job Click to see the possible cause of the failure (guessed by this bot)
|
I have returned! Supposedly, Fuchsia (and indeed Google) enables this everywhere and "there is no significant performance impact when enabling frame pointers w/ -momit-leaf-frame-pointer or the Rust equivalent of NonLeaf". They even ran LLVM for quite a while. I know they tend to run LLVM at HEAD? Let's try this bench again, then! @bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
…nters, r=<try> [DO NOT MERGE] Experimentally force non-leaf frame pointers Continuing the experiment of rust-lang#114323 r? `@ghost`
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (80a8029): comparison URL. Overall result: ❌ regressions - 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: 678.263s -> 676.946s (-0.19%) |
How does this reduce binary size, lol. |
this doesn't really accurately capture the perf impact tbh, as we're measuring both the effect of compiling the rustc binary with them and the effect of rustc compiling something with frame pointers - not that meaningful. it would be more insightful to patch bootstrap to pass the frame pointer builds flags to rustc, so we can measure the rustc binary without disturbing the way rustc compiles things - if that's what you want to measure |
but it looks like from bitmaps incremental (which shows up in cycles and wall time as well) that
|
...hmm. |
I suspect, by being told to include frame pointers, LLVM is making more deliberate decisions about inlining since it knows that now that costs a few more instructions. |
There's no |
Switching to waiting on author since it looks a work in progress, review by author themself @rustbot author |
Continuing the experiment of #114323
r? @ghost