-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
[RFC 2011] Expand expressions where possible #98148
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 47b057a with merge 025f1f8efa4f860a51b24ee27c3b76f84d254bde... |
☀️ Try build successful - checks-actions |
Queued 025f1f8efa4f860a51b24ee27c3b76f84d254bde with parent 6ec3993, future comparison URL. |
Finished benchmarking commit (025f1f8efa4f860a51b24ee27c3b76f84d254bde): comparison url. Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results
CyclesResults
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 r+ |
📌 Commit 47b057a has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (42dcf70): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
This PR, as well as some other PRS, shows that Perf is acting stochastically. |
Tracking issue: #44838
Fourth step of #96496
Extends #97665 considering expressions that are good candidates for expansion.
r? @oli-obk