-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Clean up derived obligation creation #96892
The head ref may contain hidden characters: "\u{1F40C}_obligation_cause_code_\u{1F40C}"
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 704bbe5 with merge 9701b7f9d6041dd29f744e96144781b84fde126f... |
☀️ Try build successful - checks-actions |
Queued 9701b7f9d6041dd29f744e96144781b84fde126f with parent 2226f19, future comparison URL. |
Finished benchmarking commit (9701b7f9d6041dd29f744e96144781b84fde126f): comparison url. Summary:
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 may lead to changes in compiler perf. @bors rollup=never Footnotes |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 824e9e4 with merge e3023fae71eed90e195f9053f28ad1605097ac56... |
☀️ Try build successful - checks-actions |
Sorry for the spam. This PR was causing bors to get stuck, but I think it should be cleared now. |
Without optimizations this is actually a tiny improvement on the regressed benchmark, so any further regressions are due to LLVM randomness @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 0cefa5f with merge e07108b10a51c3252d80b9ec8a6a6a1ae6fb54af... |
☀️ Try build successful - checks-actions |
Queued e07108b10a51c3252d80b9ec8a6a6a1ae6fb54af with parent 56d540e, future comparison URL. |
Finished benchmarking commit (e07108b10a51c3252d80b9ec8a6a6a1ae6fb54af): comparison url. Summary:
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 may lead to changes in compiler perf. @bors rollup=never Footnotes |
Oh yea, I won at inlining golf against LLVM @rustbot ready |
@@ -339,17 +331,17 @@ impl<'a, 'tcx> WfPredicates<'a, 'tcx> { | |||
}) | |||
.filter(|(_, arg)| !arg.has_escaping_bound_vars()) | |||
.map(|(i, arg)| { | |||
let mut new_cause = cause.clone(); | |||
let mut cause = traits::ObligationCause::misc(self.span, self.body_id); |
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.
Out of curiosity, could we keep the original clause
as part of a chain? I wonder if this would improve the output.
@bors r+ |
📌 Commit 0cefa5f has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (c1d65ea): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
r? @estebank
working on fixing the perf regression from #91030 (comment)