Uh oh!
There was an error while loading. Please reload this page.
Add an ensure_sufficient_stack to LateContextAndPass::visit_expr - #112673
Conversation
This is apparently where it's busting stack, and the comments for `ensure_sufficient_stack` say that > E.g. almost any call to visit_expr or equivalent can benefit from this.
rustbot
commented
Jun 15, 2023
r? @fee1-dead (rustbot has picked a reviewer for you, use r? to override) |
scottmcm
commented
Jun 15, 2023
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
bors
commented
Jun 15, 2023
⌛ Trying commit 44789b6 with merge 642b1ef2eaed49f8155bef08684b75112fbb432e... |
bors
commented
Jun 15, 2023
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
rust-timer
commented
Jun 15, 2023
Finished benchmarking commit (642b1ef2eaed49f8155bef08684b75112fbb432e): comparison URL. Overall result: ❌ regressions - 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 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.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 648.042s -> 648.077s (0.01%) |
compiler-errors
commented
Jun 16, 2023
👍 yeah if this isn't perf sensitive then I don't see why not r? @compiler-errors@bors r+ |
bors
commented
Jun 16, 2023
bors
commented
Jun 16, 2023
bors
commented
Jun 16, 2023
☀️ Test successful - checks-actions |
rust-timer
commented
Jun 16, 2023
Finished benchmarking commit (0966f32): comparison URL. Overall result: ❌ regressions - no action needed@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 sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 647.175s -> 648.963s (0.28%) |
This is apparently where it's busting stack in #112238, and the comments for
ensure_sufficient_stacksay thatSo this seems like a reasonable change.
Hopefully it'll keep this from happening in other places too -- #111818 (comment) hit something similar when updating a lint (bors failure is https://github.com/rust-lang-ci/rust/actions/runs/5199591324/jobs/9377196369), so with any luck this will keep small permutations of things from tripping over the limit.