perf test #87280

[lcnr]

slightly modified to figure out where the regression is coming from

cc #87280
r? @ghost

[lcnr]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit 08b62679f832a8b458ecede284807ba4994c9e32 with merge d14be679290d89abfb8d698975d47a816e3a30b4...

[bors]

💔 Test failed - checks-actions

[bors]

☔ The latest upstream changes (presumably #86461) made this pull request unmergeable. Please resolve the merge conflicts.

[lcnr]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit 41d1486e11d7d1c2dea2179e449bb7e8e44d7a75 with merge 906e14b8a1c37638d5227149717e52bba78c9bd5...

[bors]

☀️ Try build successful - checks-actions
Build commit: 906e14b8a1c37638d5227149717e52bba78c9bd5 (906e14b8a1c37638d5227149717e52bba78c9bd5)

[rust-timer]

Queued 906e14b8a1c37638d5227149717e52bba78c9bd5 with parent 70f7471, future comparison URL.

[rust-timer]

Finished benchmarking try commit (906e14b8a1c37638d5227149717e52bba78c9bd5): comparison url.

Summary: This change led to significant regressions 😿 in compiler performance.

• Very large regression in instruction counts (up to 14.5% on full builds of ctfe-stress-4-check)

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 @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf +perf-regression

[lcnr]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit ac752bfab3d933a774f4d0d49ef1204bfb0123b8 with merge a04ea67a5182d089f522d6fdc21c69404b3447c4...

[bors]

☀️ Try build successful - checks-actions
Build commit: a04ea67a5182d089f522d6fdc21c69404b3447c4 (a04ea67a5182d089f522d6fdc21c69404b3447c4)

[rust-timer]

Queued a04ea67a5182d089f522d6fdc21c69404b3447c4 with parent effea9a, future comparison URL.

[rust-timer]

Finished benchmarking try commit (a04ea67a5182d089f522d6fdc21c69404b3447c4): comparison url.

Summary: This change led to significant regressions 😿 in compiler performance.

• Very large regression in instruction counts (up to 15.5% on full builds of ctfe-stress-4-check)

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 @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf +perf-regression

[lcnr]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit 6515738 with merge 22a1bd761de8b0ac85d9ecaae5f262d5798a4409...

[bors]

☀️ Try build successful - checks-actions
Build commit: 22a1bd761de8b0ac85d9ecaae5f262d5798a4409 (22a1bd761de8b0ac85d9ecaae5f262d5798a4409)

[rust-timer]

Queued 22a1bd761de8b0ac85d9ecaae5f262d5798a4409 with parent 3b5df01, future comparison URL.

[rust-timer]

Finished benchmarking try commit (22a1bd761de8b0ac85d9ecaae5f262d5798a4409): comparison url.

Summary: This change led to large relevant regressions 😿 in compiler performance.

• Large regression in instruction counts (up to 3.5% on full builds of ctfe-stress-4)

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 @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf +perf-regression