[DO NOT MERGE] perf-test for #74069

[rust-timer]

This is an automatically generated pull request (from here) to run perf tests for #74069 which merged in a rollup.

        r? @ghost

[rust-timer]

@bors try @rust-timer queue

        The try commit's (master) parent should be 8ad7bc3f428300aee6764f6e23527e19eb235e81. If it isn't, then please:

          * Stop this try build (`try-`).
          * Run `@rust-timer update-pr-for e775b4dbc4a991d60014225088c58eddd91f18cb`.
          * Rerun `bors try`.

        You do not need to reinvoke the queue command as long as the perf build hasn't yet started.

[rust-timer]

Awaiting bors try build completion

[Mark-Simulacrum]

@bors try

It seems like we raced with GitHub's creation of the "pull request" merge commit...

[bors]

⌛ Trying commit e464d57 with merge cfade73820883adf654fe34fd6b0b03a99458a51...

[bors]

☀️ Try build successful - checks-actions, checks-azure
Build commit: cfade73820883adf654fe34fd6b0b03a99458a51 (cfade73820883adf654fe34fd6b0b03a99458a51)

[rust-timer]

Queued cfade73820883adf654fe34fd6b0b03a99458a51 with parent 8ad7bc3, future comparison URL.

[rust-timer]

Finished benchmarking try commit (cfade73820883adf654fe34fd6b0b03a99458a51): comparison url.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying rollup- to bors.

Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up.

@bors rollup=never

[Mark-Simulacrum]

Real comparison URL: https://perf.rust-lang.org/compare.html?start=d3df8512d2c2afc6d2e7d8b5b951dd7f2ad77b02&end=cfade73820883adf654fe34fd6b0b03a99458a51