Revert "Rollup merge of #78934 - DeveloperC286:issue_60302_vec, r=m-ou-se"

[rylev]

This is the second attempt to find the cause of the perf regression in the rollup #80530. It reverts #78934.

r? @ghost

This reverts commit 242a252, reversing
changes made to 507bff9.

[rylev]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

[bors]

⌛ Trying commit e816079 with merge 16af6f17ca2d426cb8a8883fdb0c083de796ffac...

[bors]

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

[rust-timer]

Queued 16af6f17ca2d426cb8a8883fdb0c083de796ffac with parent 3d8608a, future comparison URL.

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

[rust-timer]

Finished benchmarking try commit (16af6f17ca2d426cb8a8883fdb0c083de796ffac): 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
@rustbot label: +S-waiting-on-review -S-waiting-on-perf

[rylev]

This seems to be the likely culprit.

[Mark-Simulacrum]

Yeah, I'm guessing this is something we should just led slide for now - seems to be CGU partitioning and I don't think it's worth reverting.

[rylev]

I think we should investigate the cause of the perf issues, but I agree there's no reason to actually revert this change.