-
Notifications
You must be signed in to change notification settings - Fork 213
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
Inconsistent truncation of -0.0 #617
Comments
Ok this is actually the builtin symbol doing the wrong thing. f64 -> f32 keeps the sign for -0, as does rustc_apfloat, so I think compiler-builtins is correct here. |
Even more float conversions seem wrong on some platforms when called directly. E.g.
I am getting these from the benchmark tests that call external symbols rather than assembly #617 |
On
Interestingly, that test seems to pass on the i686 Windows targets |
Perhaps this is due to an issue in libgcc's implementation of these functions? |
I suppose so. I need to dig a bit more into what is actually getting linked, I'll open issues in the relevant projects once I can reproduce them in C. |
Few more inconsistencies where it seems like the system symbol is wrong. I guess we are testing against the correct assembly versions, but the named symbols available are wrong. On i586-unknown-linux-gnu:
On powerpc64le-unknown-linux-gnu:
Possibly related to the other ABI problems like llvm/llvm-project#92246. Also on
|
The text was updated successfully, but these errors were encountered: