-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Shrink Nonterminal
#95715
Shrink Nonterminal
#95715
Conversation
35177ca
to
eeac90f
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit eeac90f18e23e5b7424093d37a35063ec6515717 with merge 3f4e6015c84c484c82557eb51dcc29431d322233... |
This comment has been minimized.
This comment has been minimized.
eeac90f
to
5a9aeb4
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 5a9aeb4a4491b3718709e43d32e862d3db2edd63 with merge c985d860700830a89222e7893aaab3aa247a37ba... |
This comment has been minimized.
This comment has been minimized.
☀️ Try build successful - checks-actions |
Queued c985d860700830a89222e7893aaab3aa247a37ba with parent bbe9d27, future comparison URL. |
Finished benchmarking commit (c985d860700830a89222e7893aaab3aa247a37ba): 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 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 Footnotes |
Some max-RSS wins on |
5a9aeb4
to
1937012
Compare
The I've pushed a new version of the code that is less invasive, it does the minimal thing for @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 1937012199dc0d95f70852ff893dc0794b05e0b2 with merge 209128933ec993c4bab7e0994fa2b2bc81f81f39... |
This comment has been minimized.
This comment has been minimized.
☀️ Try build successful - checks-actions |
Queued 209128933ec993c4bab7e0994fa2b2bc81f81f39 with parent 8f36334, future comparison URL. |
Finished benchmarking commit (209128933ec993c4bab7e0994fa2b2bc81f81f39): 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 led to changes in compiler perf. @bors rollup=never Footnotes |
By heap allocating the argument within `NtPath`, `NtVis`, and `NtStmt`. This slightly reduces cumulative and peak allocation amounts, most notably on `deep-vector`.
1937012
to
d9592c2
Compare
r? @davidtwco |
Some small but clear wins, definitely worth it for the small changes. |
@bors r+ |
📌 Commit d9592c2 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (fa72316): comparison url. Summary:
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 Footnotes |
Small consistency and performance improvements.
r? @petrochenkov