[perf only] Try to disable deferred inlining

[nikic]

Just to see what the perf effect is...

r? @ghost

[nikic]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

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

[bors]

⌛ Trying commit 453771a with merge 07378cd9e76010238f64ea03d1219774eb60510d...

[bors]

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

[rust-timer]

Queued 07378cd9e76010238f64ea03d1219774eb60510d with parent 3b263ce, future comparison URL.

[rust-timer]

Finished benchmarking commit (07378cd9e76010238f64ea03d1219774eb60510d): comparison url.

Summary: This change led to very large relevant mixed results 🤷 in compiler performance.

• Very large improvement in instruction counts (up to -8.4% on incr-patched: println builds of regression-31157)
• Large regression in instruction counts (up to 2.4% on incr-full builds of deeply-nested)

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

[camelid]

I'm going to close this since AIUI, it was just a perf test. Please re-open if that's not the case.