Issues in virtual machines related to SSE2+ usage following GCC 13 upgrade

[waddlesplash]

This is a meta-ticket created to encompass the various symptoms which seem to have implicit SSE2 usage from GCC 13 optimizations as a common cause.

In summary:

• QEMU/KVM: Hangs on rocket during network device initialization, "emulation failure" in console (#18541), sometimes reports as "paused" (#18562)

• Hyper-V: GPEs, SMEP volations, READ/WRITE FAULTs in KDL, etc. (#18550)

• VMware: READ/WRITE FAULT on KDL backtraces into userland, area contains, and a bunch of other KDL commands (seen in #17233.)

The issues in QEMU/KVM do not occur in VMware and vice versa. Compiling the kernel and drivers with -mno-sse2 (i.e. leaving SSE(1) enabled for standard floating-point usage) seems to resolve the problems.

[waddlesplash]

Note: regular QEMU without KVM doesn't have any issues, it works fine. To my knowledge, note of these problems reproduce on bare metal, either.

[waddlesplash]

The problem isn't related to usage of XSAVE, it appears. I disabled that in arch_cpu.cpp and the problems in VMware noted above persisted.

[waddlesplash]

Disabled autovectorization in hrev57286, which should "fix" the above problems.