[perf only] Test SimplifyCFG patch

[nikic]

Perf test for https://reviews.llvm.org/D116692.

r? @ghost

[nikic]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

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

[bors]

⌛ Trying commit 7411334 with merge 4855d02ff6d02b33d0cd181f5e574ad17c2e6284...

[bors]

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

[rust-timer]

Queued 4855d02ff6d02b33d0cd181f5e574ad17c2e6284 with parent e4ff903, future comparison URL.

[rust-timer]

Finished benchmarking commit (4855d02ff6d02b33d0cd181f5e574ad17c2e6284): 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

[nikic]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

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

[bors]

⌛ Trying commit 13481be with merge 536b3684039689d2e0649d093ad6d4e15479d6fa...

[bors]

☔ The latest upstream changes (presumably #87648) made this pull request unmergeable. Please resolve the merge conflicts.

[bors]

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

[rust-timer]

Queued 536b3684039689d2e0649d093ad6d4e15479d6fa with parent 7531d2f, future comparison URL.

[rust-timer]

Finished benchmarking commit (536b3684039689d2e0649d093ad6d4e15479d6fa): 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