Displaying 4 results from an estimated 4 matches for "_fixxfdi".
2007 Sep 19
2
[LLVMdev] Building current llvm-gcc-4.0 TOT fails on darwin x86
...-I. -I. -I../../llvm-gcc-4.0/gcc -I../../
llvm-gcc-4.0/gcc/. -I../../llvm-gcc-4.0/gcc/../include -I./../intl -
I../../llvm-gcc-4.0/gcc/../libcpp/include -I/Users/arnold/Desktop/
testing/vanilla-gcc-4.0/llvm/include -I/Users/arnold/Desktop/testing/
vanilla-gcc-4.0/obj/../build/include -m64 -DL_fixxfdi -
fvisibility=hidden -DHIDE_EXPORTS -c ../../llvm-gcc-4.0/gcc/libgcc2.c
-o libgcc/x86_64/_fixxfdi.o
Formal argument #0 has unhandled type f80
../../llvm-gcc-4.0/gcc/libgcc2.c:1235: internal compiler error: Abort
trap
will disable multilib (./configure --disable-multilib ...) and try
again a...
2007 Sep 19
0
[LLVMdev] Building current llvm-gcc-4.0 TOT fails on darwin x86
..../llvm-gcc-4.0/gcc -I../../
> llvm-gcc-4.0/gcc/. -I../../llvm-gcc-4.0/gcc/../include -I./../intl -
> I../../llvm-gcc-4.0/gcc/../libcpp/include -I/Users/arnold/Desktop/
> testing/vanilla-gcc-4.0/llvm/include -I/Users/arnold/Desktop/testing/
> vanilla-gcc-4.0/obj/../build/include -m64 -DL_fixxfdi -
> fvisibility=hidden -DHIDE_EXPORTS -c ../../llvm-gcc-4.0/gcc/libgcc2.c
> -o libgcc/x86_64/_fixxfdi.o
> Formal argument #0 has unhandled type f80
> ../../llvm-gcc-4.0/gcc/libgcc2.c:1235: internal compiler error: Abort
> trap
>
> will disable multilib (./configure --disable-mu...
2007 Sep 19
0
[LLVMdev] Building current llvm-gcc-4.0 TOT fails on darwin x86
I think the build should work now, could you try? You need both
llvm and llvm-gcc.
There are still codegen issues, but I don't think they'll affect code
that
doesn't use long double.
On Sep 19, 2007, at 8:01 AM, Arnold Schwaighofer wrote:
> Okay dokey, thanks :)
> On 19 Sep 2007, at 16:52, Dale Johannesen wrote:
>>> message. Is that a just a temporary inconsistency
2007 Sep 19
4
[LLVMdev] Building current llvm-gcc-4.0 TOT fails on darwin x86
Okay dokey, thanks :)
On 19 Sep 2007, at 16:52, Dale Johannesen wrote:
>> message. Is that a just a temporary inconsistency or should i file a
>> bug?
>
> I think I broke this with long double. I'll get it fixed shortly.