-
Notifications
You must be signed in to change notification settings - Fork 13.3k
WASM compilation broken on nightly? #53390
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
Comments
Now pushed to stable 1.29. Great. |
Ah it looks like this is a symbol conflict error:
You'll want to rename your |
Oh, I see, thanks! |
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Sep 15, 2018
Historically LLD has emitted warnings for various reasons but all the bugs have since been fixed (yay!) and by enabling fatal warnings we should be able to head off bugs like rust-lang#53390 sooner.
kennytm
added a commit
to kennytm/rust
that referenced
this issue
Sep 20, 2018
…eddyb Enable fatal warnings for the wasm32 linker Historically LLD has emitted warnings for various reasons but all the bugs have since been fixed (yay!) and by enabling fatal warnings we should be able to head off bugs like rust-lang#53390 sooner.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A thing works fine when compiled with stable rust, but fails at runtime with nightly.
I tried this code:
https://github.com/jD91mZM2/jD91mZM2.github.io
I expected this to happen:
It'd compile and work, just like it used to.
Instead, this happened:
It appears it has to do something with
Specifically, changing them to take f64 instead fails with:
Meta
rustc --version --verbose
:The text was updated successfully, but these errors were encountered: