-
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
perf: only check for rustc_trivial_field_reads
attribute on traits, not items, impls, etc.
#89454
Conversation
The checks removed here caused a small perf regression: rust-lang#88824 (comment) Since the attribute is currently only applied to traits, I don't think it's worth keeping the additional checks for now. If/when we decide to apply the attribute somewhere else, we can (partially) revert this and evaluate if the perf impact is acceptable.
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit eb4ba58 with merge 6af27bf535758296bda5cf8bf2a01bd4b1764c1a... |
☀️ Try build successful - checks-actions |
Queued 6af27bf535758296bda5cf8bf2a01bd4b1764c1a with parent 6e12110, future comparison URL. |
Finished benchmarking commit (6af27bf535758296bda5cf8bf2a01bd4b1764c1a): comparison url. Summary: This change led to moderate 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 |
Can I get another perf run? |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit bec5a91 with merge c5f130816ee1458aa21bba39bf47f9c849e696a6... |
☀️ Try build successful - checks-actions |
Queued c5f130816ee1458aa21bba39bf47f9c849e696a6 with parent b27661e, future comparison URL. |
Finished benchmarking commit (c5f130816ee1458aa21bba39bf47f9c849e696a6): comparison url. Summary: This change led to moderate 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 |
@bors r+ |
📌 Commit bec5a91 has been approved by |
⌛ Testing commit bec5a91 with merge f0cbd0e4677561339dd252ac2c1281b69d42ddad... |
💔 Test failed - checks-actions |
A job failed! Check out the build log: (web) (plain) Click to see the possible cause of the failure (guessed by this bot)
|
☀️ Test successful - checks-actions |
Finished benchmarking commit (d3e6770): comparison url. Summary: This change led to moderate relevant improvements 🎉 in compiler performance.
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
The checks that are removed in this PR (originally added in #85200) caused a small perf regression: #88824 (comment)
Since the attribute is currently only applied to traits, I don't think it's worth keeping the additional checks for now.
If/when we decide to apply the attribute somewhere else, we can (partially) revert this and reevaluate the perf impact.
r? @nikomatsakis cc @FabianWolff