-
Notifications
You must be signed in to change notification settings - Fork 13.4k
borrowck::mir::dataflow: ignore unwind edges of empty drops #41148
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
Conversation
@@ -74,6 +76,66 @@ impl<'tcx> MirPass<'tcx> for ElaborateDrops { | |||
|
|||
impl Pass for ElaborateDrops {} | |||
|
|||
/// Return the set of basic blocks whose unwind terminators are known |
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.
I find this comment worded somewhat weirdly. What are the “unwind terminators”? Do you mean the branch that comes out from the terminator, maybe?
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.
This looks good. The comment seems somewhat weird in how it is worded, but I don’t mind it much.
r=me
This avoids creating drop flags in many unnecessary situations. Fixes rust-lang#41110.
@bors r=nagisa |
📌 Commit 6979798 has been approved by |
⌛ Testing commit 6979798 with merge 666e714... |
borrowck::mir::dataflow: ignore unwind edges of empty drops This avoids creating drop flags in many unnecessary situations. Fixes #41110. r? @nagisa beta-nominating because regression. However, that is merely a small perf regression and codegen changes are always risky, so we might let this slide for 1.17.
☀️ Test successful - status-appveyor, status-travis |
Decided it is not worth it to backport. |
This avoids creating drop flags in many unnecessary situations.
Fixes #41110.
r? @nagisa
beta-nominating because regression. However, that is merely a small perf regression and codegen changes are always risky, so we might let this slide for 1.17.