-
Notifications
You must be signed in to change notification settings - Fork 13k
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
binaryen is being built with inappropriate compiler flags for i586-unknown-linux-gnu host #49267
Comments
Just a note, the offending code seems to be in src/binaryen/CMakeLists.txt |
Note that binaryen has been removed in Rust 1.26 (by #48125), which will enter beta next week. |
After looking into this a bit further, the binaryen folks have force-enabled sse2 with the note "wasm doesn't allow for x87 floating point math". I suppose this is referring to issues with precision/rounding when doing calculations with constants while compiling to wasm? It's unclear how much of a problem this might actually be. If disabling sse operations in binaryen isn't an option, then the only way to get an i586 rustc build working again would be to allow disabling binaryen and the wasm target. Edit: Missed a comment - the binaryen removal in 1.26 should solve this issue. |
I've cross-compiled a nightly rustc from after the #48125 merge, and I've confirmed that the result is able to bootstrap nightly rustc on my i586 box. I'm gonna consider this issue fixed - looking forwards to the beta release. |
I've been trying to get an i586-unknown-linux-gnu build of rustc 1.24.1 going for a while, and I've gotten close, but the final rustc binary is crashing with an illegal instruction:
When looking into it, this particular piece of code is from the native binaryen library. From the build log
build/i586-unknown-linux-gnu/stage0-rustc/i586-unknown-linux-gnu/release/build/rustc_binaryen-b307d012dc0782fb/output
:It's building with the compiler options
-msse2 -mfpmath=sse
which should not be used on the i586 target.The text was updated successfully, but these errors were encountered: