-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
f32::rem fails on wasm32-unknown-emscripten #42629
Comments
Add a travis builder for wasm32-unknown-emscripten This commits add an entry to travis matrix that will execute wasm32-unknown-emscripten tests suites. - Emscripten for asmjs was updated to sdk-1.37.13-64bit - The tests are run with node 8.0.0 (it can execute wasm) - A wrapper script is used to run each test from the directory where it is (workaround for emscripten-core/emscripten#4542) - Some tests are ignore, see #42629 and #42630
Looks like my code has also hit this bug: https://travis-ci.org/CryZe/livesplit-core/jobs/255487184#L401 Do we know where this bug is? If so, I probably want to try to fix it. It seems like in my case I don't even have f64 at all, and yet it still uses f64-rem. |
Minimized example:
Gives following output (stripped):
It seems like problem lies in Emscripten side of things. |
Should be fixed by WebAssembly/binaryen#1106 |
Looks like upstream fix (WebAssembly/binaryen#1106) is merged so closing, yay! |
This example (test for issue #27859):
fails to compile for wasm32-unknown-emscripten with the error:
The text was updated successfully, but these errors were encountered: