Release v0.11.3 (but not v0.11.2) hangs while compiling a few specific wasm modules

[Stebalien]

Using the latest wasmtime (v31), compiling the attached wasm module with wasmtime compile hangs after updating regalloc to v0.11.3. It compiles instantly when using regalloc v0.11.2 or below.

Specifically:

1. Clone wasmtime.
2. Checkout the release-31.0.0 branch.
3. Run cargo update regalloc2 to update to v0.11.3.
4. Run cargo run --release -- compile example.wasm (--release isn't necessary but it demonstrates that it's not just slow due to running in debug mode).

See example.zip (extract it first, GitHub doesn't allow uploading raw wasm files).

I've also tried patching in the latest main branch of regalloc2 and that doesn't seem to help. This points to a bug in #214 that hasn't been fixed yet.

[cfallin]

Taking a look, thanks!

[cfallin]

FYI, I've yanked 0.11.3 because of this issue. Released Wasmtime will continue to use 0.11.2, and Wasmtime's main will use 0.11.3 via its lockfile until I can fix this and roll forward to a new RA2 version. I filed bytecodealliance/wasmtime#10562 to track.

[cfallin]

And a bit more for @Stebalien and @Mrmaxmeier (and any others affected): I'm balancing my Cranelift/regalloc2 work with some internal work as well, and need to timeslice back to that; given that the above crate yank removed the immediate urgency, I'd recommend using the released Wasmtime with 0.11.2 until further notice, as a proper fix is going to be a somewhat nontrivial revamp to liverange splitting and minimal bundles and likely won't come in the next few days.

[Stebalien]

No problem, I'm in no rush. But thanks for yanking the crate, that makes things much simpler on my end.