-
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
Revert "Rollup merge of #92006 - oli-obk:welcome_opaque_types_into_th… #92928
Conversation
r? @estebank (rust-highfive has picked a reviewer for you, use r? to override) |
@bors try @rust-timer queue trying to see if this fixes the perf regression of #92844 (comment) |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit fd04250 with merge 8c4a951b919d548bba16b6f209ed05b1647eba2c... |
r? @ghost |
☀️ Try build successful - checks-actions |
Queued 8c4a951b919d548bba16b6f209ed05b1647eba2c with parent 38c22af, future comparison URL. |
Finished benchmarking commit (8c4a951b919d548bba16b6f209ed05b1647eba2c): comparison url. Summary: This change led to very large relevant improvements 🎉 in compiler performance.
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking 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 led to changes in compiler perf. @bors rollup=never |
r? @oli-obk |
while !obligations.is_empty() { | ||
trace!("{:#?}", obligations); | ||
let mut progress = false; | ||
for obligation in std::mem::take(&mut obligations) { |
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 wonder if this hurts perf. We create a new Vec when we take, so we have to reallocate when new obligations are pushed.
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.
trying this out in #93007
@bors r+ |
📌 Commit fd04250 has been approved by |
@bors r- |
@bors try @rust-timer queue Let's run this again, apperently keccak is spurious recently |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit fd04250 with merge 8bf5d7c746e31951e97de80d2fa1362a1d9bbd1c... |
☀️ Try build successful - checks-actions |
Queued 8bf5d7c746e31951e97de80d2fa1362a1d9bbd1c with parent e4ff903, future comparison URL. |
Finished benchmarking commit (8bf5d7c746e31951e97de80d2fa1362a1d9bbd1c): comparison url. Summary: This change led to small relevant mixed results 🤷 in compiler performance.
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking 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 led to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never |
Yea, looks like my PR wasn't the reason for the regression, so we don't need to revert? |
I agree; I think this could be closed. |
…e_fold, r=nikomatsakis"
This reverts commit b45a819, reversing
changes made to e045c79.