-
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
Re-land PR #71840 (Rework MIR drop tree lowering) #77466
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion |
⌛ Trying commit 88d7b299d7494e8fa04144620048f90c1bf7fb47 with merge ebcdd716a8c89036fe844c7d6c6630327ed52639... |
cc @oli-obk who originally reviewed this. |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
💔 Test failed - checks-actions |
d805562
to
eabd931
Compare
@bors try |
⌛ Trying commit eabd931751af6ebca454f26286c9a7288df9085f with merge 90dc169bb6d89043121e001959a263fc83466079... |
☀️ Try build successful - checks-actions, checks-azure |
Queued 90dc169bb6d89043121e001959a263fc83466079 with parent 8876ffc, future comparison URL. |
Finished benchmarking try commit (90dc169bb6d89043121e001959a263fc83466079): 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for reviving this. r=me with comments addressed.
@bors r=matthewjasper |
📌 Commit 045ef67eef1b32be4ccc664b398c463083f79f64 has been approved by |
⌛ Testing commit 045ef67eef1b32be4ccc664b398c463083f79f64 with merge 24a29ed9b08920c1f10ad615662b1b3a0396ba1c... |
💔 Test failed - checks-actions |
Co-authored-by: matthewjasper <[email protected]>
045ef67
to
b617bbb
Compare
I didn't have @bor r=matthewjasper |
@bors r=matthewjasper |
📌 Commit b617bbb23ae20286fe72a01ecb8c5f5f49a29a6c has been approved by |
⌛ Testing commit b617bbb23ae20286fe72a01ecb8c5f5f49a29a6c with merge 8cb662339371f7fed8fe376b7ed914c80ef1ac74... |
💔 Test failed - checks-actions |
b617bbb
to
ce8d757
Compare
@bors r=matthewjasper |
📌 Commit ce8d757 has been approved by |
☀️ Test successful - checks-actions, checks-azure |
Final perf results are in. Looks like a small win across the board, with one exception. Thanks all! |
PR #71840 was reverted in #72989 to fix an LLVM error (#72470). That LLVM error no longer occurs with the recent upgrade to LLVM 11 (#73526), so let's try re-landing this PR.
I've cherry-picked the commits from the original PR (with the exception of the commit blessing test output), making as few modifications as possible. I addressed the rebase fallout in separate commits on top of those.
r? @matthewjasper