Displaying 3 results from an estimated 3 matches for "target_zarch".
Did you mean:
target_arch
2009 Oct 30
0
[LLVMdev] llvm-gcc-4.2 RELEASE_26 bootstrap failure on Solaris/SPARC - unhandled REAL_TYPE during compilation of '__powitf2'
...ct {double, double} as you already saw and sparc currently
does not provide any argument layout hooks.
There are two possible solutions for a moment:
1. Temporary turn 128-bit fp into 64-bit fp (there should be some
define in config/sparc/*)
2. Turn 128bit fp into normal first-class type (grep for TARGET_ZARCH
into llvm-types.cpp, where this mapping is done for s390x), but then
you will need to implement all codegen for 128-bit fp, since sparc
backend is currently really weak.
--
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University
2009 Oct 30
2
[LLVMdev] llvm-gcc-4.2 RELEASE_26 bootstrap failure on Solaris/SPARC - unhandled REAL_TYPE during compilation of '__powitf2'
Hi Anton,
thanks for the fast response.
Ty->dump() prints "{double, double}" in the failing case (just before my
introduced assert).
HTH, and regards,
Juergen
On 10/30/09 16:19, Anton Korobeynikov wrote:
> Hello, Juergen
>
>> With the full patch, I get the assertion of the 'unhandled REAL_TYPE!',
>> so I wonder what needs to be done in order to get
2009 Nov 02
1
[LLVMdev] llvm-gcc-4.2 RELEASE_26 bootstrap failure on Solaris/SPARC - unhandled REAL_TYPE during compilation of '__powitf2'
...eady saw and sparc currently
> does not provide any argument layout hooks.
>
> There are two possible solutions for a moment:
> 1. Temporary turn 128-bit fp into 64-bit fp (there should be some
> define in config/sparc/*)
> 2. Turn 128bit fp into normal first-class type (grep for TARGET_ZARCH
> into llvm-types.cpp, where this mapping is done for s390x), but then
> you will need to implement all codegen for 128-bit fp, since sparc
> backend is currently really weak.
>
--
Sun Microsystems GmbH Juergen Zimmermann
Altrottstrasse 31 ISV Engineering EMEA, Technical Lead for S...