-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Perf experiment for "Get piece unchecked in write
"
#88571
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
r? @wesleywiser (rust-highfive has picked a reviewer for you, use r? to override) |
@bors try @rust-timer queue include=style-servo |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit bf164323aa3c5516b301411f7194ca24286297d5 with merge 6234197c9036b92e2061fe61b9d14a6b100556bb... |
☀️ Try build successful - checks-actions |
Queued 6234197c9036b92e2061fe61b9d14a6b100556bb with parent 50171c3, future comparison URL. |
Finished benchmarking try commit (6234197c9036b92e2061fe61b9d14a6b100556bb): 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 perf run, please indicate this with @bors rollup=never |
Avoids two nested `matche`es but widens the scope of the unsafe block.
bf16432
to
1db96e3
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 1db96e3 with merge fd20cc804e82e71d4bb692b455556865f14d7677... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
☀️ Try build successful - checks-actions |
Queued fd20cc804e82e71d4bb692b455556865f14d7677 with parent 6492931, future comparison URL. |
Finished benchmarking try commit (fd20cc804e82e71d4bb692b455556865f14d7677): comparison url. Summary: ERROR categorizing benchmark run! Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. @bors rollup=never |
Seeing if I can find the cause of the perf regression #83302 by reverting parts.
@bors try @rust-timer queue include=style-servo-debug