> Okay, but such a bug means Rust is not ready for prime time yet
Does the presence of miscompilations in GCC mean that GCC is not ready for prime time?
Does the presence of miscompilations in GCC mean that GCC is not ready for prime time?
We can't fix it fully in rustc because we don't know the stack size, which can grow with aggressive inlining, for example.
I suppose we could summarily probe allocas we know are larger than the page size, which would solve this particular situation (one large variable), but it's not a panacea.