-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Revert "Rollup merge of #80458 - RalfJung:promotion-refactor, r=oli-obk" #80727
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
r? @ghost |
@bors try @rust-timer queue |
Awaiting bors try build completion. |
⌛ Trying commit 39bbc1e with merge aaff735c88fc1381b649ee416dd34a8338c49f67... |
I am fairly certain it can't be due to this PR, since the regression is solely in LLVM optimizations, but let's wait for perf, maybe we promote fewer things now and that makes LLVM take longer (there was a change in that PR that could be breaking, but we have no examples that could even trigger that code)? |
☀️ Try build successful - checks-actions |
Queued aaff735c88fc1381b649ee416dd34a8338c49f67 with parent 68ec332, future comparison URL. @rustbot label: +S-waiting-on-perf |
☀️ Try build successful - checks-actions |
Finished benchmarking try commit (aaff735c88fc1381b649ee416dd34a8338c49f67): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
@oli-obk is correct. It’s not this PR. The search continues. |
Reverts #80458 to test for possible performance regressions.
In the latest perf triage, the rollup that the reverted PR was a part of featured a performance regression. We are testing whether the reverted PR was indeed (at least partially) responsible.
This reverts commit 46111c1, reversing
changes made to 1975142.
cc @RalfJung @oli-obk