> If you have problems with Clang, please file bugs!
Filing compiler bugs is really hard with a closed source project.
> If you have problems with Clang, please file bugs!
Filing compiler bugs is really hard with a closed source project.
God saves a puppy anytime someone filed a compiler bug with a trivial test case that demonstrates the problem.
The current (r10e) shipping version of clang cannot return 128bit floats from a function.
#include <iostream>
int main(int c, char **v) {
std::stringstream("1.5");
double x; s >> x;
return x == 1.5 ? 0 : 1;
}
EDIT: You don't need "long double" in the above. double (or float) will show the problem. The standard library converts all floating point numbers to long double internally.I see mention of long double in your edit, but even then wasn't that 80bit on PC architecture. Only Solaris and HP-UX? defined that as 128bit.
#include <iostream>
#include <sstream>
int main(int c, char **v) {
std::stringstream s("1.5");
double x; s >> x;
return x == 1.5 ? 0 : 1;
}
Apple LLVM version 7.0.2 (clang-700.1.81)
Target: x86_64-apple-darwin15.2.0
Thread model: posixI wonder if the bug you are seeing is a result of the C++ STL and not the compiler itself. Can you try reproing with libc++?
In any event, you can file bugs here: https://code.google.com/p/android/issues/list?q=label:Compon...
""" We’ve moved our bug tracker to GitHub: https://github.com/android-ndk/ndk/issues """