-
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
Test some panic!()-related perf things #92140
Conversation
This allows us to use `panic!` and friends in a const-stable context within libcore.
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 3c0d5ee with merge 8c6bc808c5e11716651cfe45f58547b97a96ff39... |
☀️ Try build successful - checks-actions |
Queued 8c6bc808c5e11716651cfe45f58547b97a96ff39 with parent 23f6923, future comparison URL. |
Finished benchmarking commit (8c6bc808c5e11716651cfe45f58547b97a96ff39): 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 |
Use panic() instead of panic!() in some places in core. See rust-lang#92068 and rust-lang#92140. This avoids the `panic!()` macro in a few potentially hot paths. This becomes more relevant when switching `core` to Rust 2021, as it'll avoid format_args!() and save some compilation time. (It doesn't make a huge difference, but still.) (Also the errors in const panic become slightly nicer.)
Trying out some stuff on top of #92068 to track down a perf issue.