-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Eliminate ConstnessAnd again #91549
Eliminate ConstnessAnd again #91549
Conversation
Some changes occurred in src/tools/clippy. cc @rust-lang/clippy Some changes occured to the CTFE / Miri engine cc @rust-lang/miri Some changes occured to the CTFE / Miri engine cc @rust-lang/miri |
@bors r+ |
📌 Commit 2304b061e4daf677f4ffc16f138ca82dd6b9d879 has been approved by |
@bors r- Should check whether this also solves the duplicate query evals |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 2304b061e4daf677f4ffc16f138ca82dd6b9d879 with merge 826335d7ca7f2dac1507ef05f329437f4ebe6caf... |
☀️ Try build successful - checks-actions |
Queued 826335d7ca7f2dac1507ef05f329437f4ebe6caf with parent 6c189bc, future comparison URL. |
Finished benchmarking commit (826335d7ca7f2dac1507ef05f329437f4ebe6caf): comparison url. Summary: This change led to moderate 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 |
Requesting another perf run as I have tried to improve performance in recent commits. @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 3eaadbda9403bd62c9c56725df9ccae8228b3077 with merge 8a028f2d4744e089b8bdd970a21eb062f830255b... |
☔ The latest upstream changes (presumably #91555) made this pull request unmergeable. Please resolve the merge conflicts. |
☀️ Try build successful - checks-actions |
Queued 8a028f2d4744e089b8bdd970a21eb062f830255b with parent 1597728, future comparison URL. |
@bors r=spastorino |
📌 Commit ffc9082 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (22f8bde): 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. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression |
@rustbot label: +perf-regression-triaged The only change between the last perf triage comment and the regression after the merge is a rebase. The exact cause is unknown, but I'm speculating CGU division and/or inlining differences. The regressions aren't "noise", but some of them are not related to the visible changes this PR has. this is like #87688 (comment), but the exact details could differ. |
Eliminate ConstnessAnd again Closes rust-lang#91489. Closes rust-lang#89432. Reverts rust-lang#91491. Reverts rust-lang#89450. r? `@spastorino`
Closes #91489.
Closes #89432.
Reverts #91491.
Reverts #89450.
r? @spastorino