Displaying 3 results from an estimated 3 matches for "float128".
Did you mean:
__float128
2016 Dec 12
1
Problem about 128bit floating-point operations in x86 machines
...ed the code for 128bit floating-point operations and tested these
operations in i686, x86_64, SPARCv8 and SPARCv9 machines.
Generated codes by LLVM operated normally when using x86_64, SPARCv8 and
SPARCv9 machines, but generated codes in a x86 machine produce wrong
result.
Because Clang supports __float128 type, I also tried to test using Clang
3.9 version.
However, I could not get the correct result of 128bit floating-point
operations using Clang.
For example, C source code that included operations of 128bit
floating-point is as follows:
#include <stdio.h>
#include <quadmath.h>
int ma...
2018 Dec 23
3
How to compile glibc with clang/llvm?
...is work, including additional configure options mentioned
below.
The minimum version of clang is 6.0.0. If lld is to be used for linking,
it needs to be newer than 6.0.0.
Configure:
CC=path-to-llvm/clang CXX=path-to-llvm/clang++ \
../glibc/configure --disable-werror --with-clang --disable-float128 \
--with-lld --with-default-link --disable-multi-arch --prefix=/something
------------------------------------------------------------------------------
On 23/12/2018 02:51, Kristina Brooks wrote:
> Hi.
>
> I've managed to do it before, with a lot of patches to Glibc, as well a...
2018 Dec 22
3
How to compile glibc with clang/llvm?
To whom it may concern,
Is there a way to build glibc with clang/llvm? I’m working on enabling llvm-cov for my compiler which is a totally new arch with a libc.a built from newlib. I successfully built compiler-rt but when I typed the command ` clang++ --target=xxx -fprofile-instr-generate -fcoverage-mapping foo.cc -o foo`, the linker failed because of undefined reference to