[EXPERIMENT] rustdoc: Mark Context::tcx() as #[inline(always)]

[camelid]

I'm wondering if tcx() not being inlined could be affecting the perf in #90391.

r? @ghost

[camelid]

It could also make sense to move tcx out of shared, since it's behind an Rc.

For now, let's see what effect this has.

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

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

[bors]

⌛ Trying commit 44b342e with merge 01cff54ade7465331b57967fce4ed7060b1a1971...

[bors]

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

[rust-timer]

Queued 01cff54ade7465331b57967fce4ed7060b1a1971 with parent e99963c, future comparison URL.

[rust-timer]

Finished benchmarking commit (01cff54ade7465331b57967fce4ed7060b1a1971): 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

[camelid]

Hmm, mixed or slightly negative results.