-
Notifications
You must be signed in to change notification settings - Fork 95
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
Some symbols reference libcore panicking functions #129
Comments
japaric
added a commit
that referenced
this issue
Jul 25, 2018
this eliminates panicking branches in the optimized version of the functions. We keep the bounds checks when running the test suite to check that we never do an out of bounds access. This commit also adds a "must link" test that ensures that future changes in our implementation won't add panicking branches. closes #129
bors bot
added a commit
that referenced
this issue
Jul 25, 2018
131: omit bounds check in release mode r=japaric a=japaric this eliminates panicking branches in the optimized version of the functions. We keep the bounds checks when running the test suite to check that we never do an out of bounds access. This commit also adds a "must link" test that ensures that future changes in our implementation won't add panicking branches. closes #129 Co-authored-by: Jorge Aparicio <[email protected]>
bors bot
added a commit
that referenced
this issue
Jul 25, 2018
131: omit bounds check in release mode r=japaric a=japaric this eliminates panicking branches in the optimized version of the functions. We keep the bounds checks when running the test suite to check that we never do an out of bounds access. This commit also adds a "must link" test that ensures that future changes in our implementation won't add panicking branches. closes #129 Co-authored-by: Jorge Aparicio <[email protected]>
bors bot
added a commit
that referenced
this issue
Jul 25, 2018
131: omit bounds check in release mode r=japaric a=japaric this eliminates panicking branches in the optimized version of the functions. We keep the bounds checks when running the test suite to check that we never do an out of bounds access. This commit also adds a "must link" test that ensures that future changes in our implementation won't add panicking branches. closes #129 Co-authored-by: Jorge Aparicio <[email protected]>
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Jul 26, 2018
Pull in a fix for rust-lang/libm#129
This was referenced Jul 26, 2018
bors
added a commit
to rust-lang/rust
that referenced
this issue
Jul 27, 2018
…richton Update the compiler-builtins submodule Pull in a fix for rust-lang/libm#129
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was curious to give out the new libm-for-wasm bits a spin and got a small example working, but to my surprise it imported a few functions from the environment:
which isn't good for wasm!
It looks like these are mostly around the
rem_pio2_large
function (and family of functions from the looks of it)The text was updated successfully, but these errors were encountered: