inline(always) on check_recursion_limit

[fee1-dead]

r? @oli-obk

#88558 caused a regression, this PR adds #[inline(always)] to check_recursion_limit, a possible suspect of that regression.

[oli-obk]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

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

[bors]

⌛ Trying commit b76b2c2 with merge 3d66748e5a10de468e3530099450e33554ed5bb8...

[bors]

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

[rust-timer]

Queued 3d66748e5a10de468e3530099450e33554ed5bb8 with parent cdeba02, future comparison URL.

[rust-timer]

Finished benchmarking commit (3d66748e5a10de468e3530099450e33554ed5bb8): comparison url.

Summary: This benchmark run did not return any relevant changes.

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.

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

[oli-obk]

it does get us some of the perf back (these were all small regressions in #88558)

so let's keep looking, but also

@bors r+

[bors]

📌 Commit b76b2c2 has been approved by oli-obk

[bors]

⌛ Testing commit b76b2c2 with merge a58db2e...

[bors]

☀️ Test successful - checks-actions
Approved by: oli-obk
Pushing a58db2e to master...