-
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
Move overlap_mode into trait level attribute #93348
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 291a4c335552ba97bdf641c006ce9e86f6f7fab2 with merge 107640c50fe413527be6069e6f181c54734f1b21... |
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.
r=me otherwise
@bors rollup=never |
This comment has been minimized.
This comment has been minimized.
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 think I have a better approach. Go back to the old attribute system, but put the attribute ON THE TRAIT, not the impls. Then check it once, when we start the coherence check, and pass the boolean down to the impls.
☀️ Try build successful - checks-actions |
Queued 107640c50fe413527be6069e6f181c54734f1b21 with parent a7f3757, future comparison URL. |
Finished benchmarking commit (107640c50fe413527be6069e6f181c54734f1b21): comparison url. Summary: This benchmark run shows 128 relevant regressions 😿 to instruction counts.
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 |
As we thought yesterday, memoizing the overlap mode should somewhat alleviate these new losses (and turn some of them into small improvements), in addition to regaining the losses from the previous negative impl PR (as the (Needless to mention, Niko's idea seems also worthwhile: coherence is hot, and the pairwise overlap checks already have superlinear scaling issues.) |
291a4c3
to
6a78206
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 6a78206c9a7d457b49dd481b2faa1bc548afd1a3 with merge ca75d679589565de2713c8cc6a2bc258d9604b40... |
6a78206
to
9ec1d6d
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 9ec1d6d1f44f8fc74aa754c145bfc12fdc50708b with merge b5dac1743636517402b355fd198ada684180f709... |
9ec1d6d
to
240418a
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 240418a81de2bbded99885f79171ba3bf3d14a46 with merge 07719c4f11b6c559d462b1e46ba138537cb47505... |
This comment has been minimized.
This comment has been minimized.
☀️ Try build successful - checks-actions |
Queued 07719c4f11b6c559d462b1e46ba138537cb47505 with parent 8c7f2bf, future comparison URL. |
Finished benchmarking commit (07719c4f11b6c559d462b1e46ba138537cb47505): comparison url. Summary: This benchmark run did not return any relevant results. 4 results were found to be statistically significant but too small to be relevant. 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 |
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.
r=me but one possible change would be to move overlap_mode
out so it is not stored as a field; the idea is that it is only used during construction and doesn't matter afterwards, so it doesn't have to be a field
compiler/rustc_trait_selection/src/traits/specialize/specialization_graph.rs
Outdated
Show resolved
Hide resolved
Here is a test we could use --- Without the feature gate, this gets an error. With the feature gate, I think it should pass, because we have |
240418a
to
0decf14
Compare
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.
r=me
@bors r+ |
📌 Commit 0decf14 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (498eeb7): comparison url. Summary: This benchmark run did not return any relevant results. 17 results were found to be statistically significant but too small to be relevant. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
r? @nikomatsakis
Should fix some performance regressions noted on #93175