[perf only] Test inliner patch

[nikic]

Testing impact of https://reviews.llvm.org/D98481, which would address #89524.

r? @ghost

[nikic]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

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

[bors]

⌛ Trying commit 98b1804 with merge b0d79486ff8b43e7be9999d567ba9af725d81544...

[bors]

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

[rust-timer]

Queued b0d79486ff8b43e7be9999d567ba9af725d81544 with parent 9475e60, future comparison URL.

[rust-timer]

Finished benchmarking commit (b0d79486ff8b43e7be9999d567ba9af725d81544): comparison url.

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

• Large regression in instruction counts (up to 1.0% on incr-unchanged builds of deep-vector)

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 @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