-
Notifications
You must be signed in to change notification settings - Fork 823
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Heads up about serious bug in Cranelift (Windows) #1179
Comments
Thanks for the heads-up! |
Cranelift maintainers are working on a fix, bytecodealliance/cranelift#1378 (moved to bytecodealliance/wasmtime#1216 ) |
The cranelift codebase has now moved into the wasmtime repo. Not sure what that means, they don't seem to have transferred the pull requests... |
Actually it seems to be fine. The PR has now been moved to here: bytecodealliance/wasmtime#1216 |
The upstream fix is merged finally! bytecodealliance/wasmtime#1216 |
Awesome. We upgraded to latest cranelift in the refactor. We should be able to close this issue once it lands in master |
The refactor has now landed in master, and the cranelift issue should be now solved (since we are using the latest one). Closing the issue |
Just wanted to point you guys to https://github.com/bytecodealliance/cranelift/issues/1366 .
Cranelift fails to save/restore the XMM registers as the Windows x64 calling convention requires, so the host can suffer corruption of floating point variables (or even other variables if the compiler does certain optimizations).
So if you've ever seen mysterious corruption issues on Windows, this might be it...
The text was updated successfully, but these errors were encountered: