[perf-check] Revert "Rollup merge of #88789 - the8472:rm-zip-bound, r=JohnTitor"

[JohnTitor]

This reverts commit 84fe598, reversing
changes made to 71fcb72.

r? @ghost cc #90067 (comment)

[JohnTitor]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

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

[bors]

⌛ Trying commit 63b4faa with merge d15f91eebbf502f315748c021e2bd8223aed77c1...

[bors]

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

[rust-timer]

Queued d15f91eebbf502f315748c021e2bd8223aed77c1 with parent f2707fe, future comparison URL.

[rust-timer]

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

[JohnTitor]

Seems this isn't perf-sensitive, closing but cc @Mark-Simulacrum just in case.