-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Avoid generating empty closures for fieldless enum variants #89881
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
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 494d8d6aa4b7a0a696734074e4a6b14eebec1962 with merge 7d7afc95a6a9574d764902529fa19cc2da594e57... |
☀️ Try build successful - checks-actions |
Queued 7d7afc95a6a9574d764902529fa19cc2da594e57 with parent c34ac87, future comparison URL. |
Finished benchmarking commit (7d7afc95a6a9574d764902529fa19cc2da594e57): comparison url. Summary: This change led to large relevant regressions 😿 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 |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit fe79ddaa920bcfd38a49ef2ab684131f5e33cd50 with merge 3bbb9545c8d171907de798f066108d45f8ab5676... |
☀️ Try build successful - checks-actions |
Queued 3bbb9545c8d171907de798f066108d45f8ab5676 with parent e1e9319, future comparison URL. |
Finished benchmarking commit (3bbb9545c8d171907de798f066108d45f8ab5676): comparison url. Summary: This change led to large 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 |
@bors try @rust-timer queue |
fe79dda
to
7576df5
Compare
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 7576df5d6627672e949087650d0a21527888b868 with merge f203e7849853c57f1751b7f28315bf4378ea8bf4... |
Queued a6a0adf03e9d169dd727f189f1291c4f1697aa1c with parent 65f3f8b, future comparison URL. |
Finished benchmarking commit (a6a0adf03e9d169dd727f189f1291c4f1697aa1c): comparison url. Summary: This change led to large 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 |
For many enums, this avoids generating lots of tiny stubs that need to be codegen'd and then inlined and removed by LLVM.
eab4b35
to
3228603
Compare
r? rust-lang/compiler-contributors Perf impact outside the self-bootstrap timing is likely to be not entirely noise, but is fairly small and IMO justified by the improvements in bootstrap time this patch gives. |
@bors r+ |
📌 Commit 3228603 has been approved by |
⌛ Testing commit 3228603 with merge 74f48bd1cf20b90e1de224a016d3385568c56adb... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@bors retry error writing to program database |
☀️ Test successful - checks-actions |
Finished benchmarking commit (311fa1f): 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. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression |
For many enums, this avoids generating lots of tiny stubs that need to be codegen'd and then inlined and removed by LLVM. perf shows this to be a fairly small, but significant, win on rustc bootstrap time -- with minimal impact on runtime performance (which is at times even positive).