-
Notifications
You must be signed in to change notification settings - Fork 13k
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
compiler: Stop manually extending the stack #134153
base: master
Are you sure you want to change the base?
compiler: Stop manually extending the stack #134153
Conversation
Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt Some changes occurred to the CTFE machinery cc @rust-lang/wg-const-eval Some changes occurred to the core trait solver cc @rust-lang/initiative-trait-system-refactor Some changes occurred in match lowering cc @Nadrieril Some changes occurred in match checking cc @Nadrieril changes to the core type system Some changes occurred in exhaustiveness checking cc @Nadrieril |
uh... sorry? ^^; |
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
…ms, r=<try> compiler: Stop manually extending the stack This rips out almost all calls to `ensure_sufficient_stack`, and disables the actual function itself for the handful of calls that proved too annoying to immediately rip out, for rebasing or type inference reasons. r? `@ghost`
what is the motivation for this change? presumably this will cause legitimate regressions on a mixture of both real and pathological examples. are you just trying to figure out the perf implications here? |
@compiler-errors Currently, yes, this is just a perf experiment. I am aware of the regressions because I have committed some of the regression tests that will now fail with this version of the compiler. If this stops being a perf experiment, it will come with a second commit that covers the real regressions. Hopefully with less of a performance impact in non-pathological cases. |
The job Click to see the possible cause of the failure (guessed by this bot)
|
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (0e81fd6): comparison URL. Overall result: ✅ improvements - 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 is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary -2.4%)This 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.
CyclesResults (primary -1.3%, secondary 2.6%)This 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 sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 768.372s -> 762.235s (-0.80%) |
This rips out almost all calls to
ensure_sufficient_stack
, and disables the actual function itself for the handful of calls that proved too annoying to immediately rip out, for rebasing or type inference reasons.r? @ghost