Displaying 3 results from an estimated 3 matches for "_unwind_sword".
2009 Nov 02
1
[LLVMdev] llvm-gcc-4.2 RELEASE_26 bootstrap failure on Solaris/SPARC - unhandled REAL_TYPE during compilation of '__powitf2'
...nton,
I went with the first alternative with some success.
However, now I get some errors during the build of libgcc
with 'multiply defined symbols'.
One thing I noticed is the following fact:
Definition in unwind-pe.h:
static const unsigned char *
read_sleb128 (const unsigned char *p, _Unwind_Sword *val)
---
GCC 4.2.4 bootstrapped on Solaris/SPARC
-bash-3.00$ nm unwind-dw2.o | grep read_sleb128
[9] | 1024| 84|FUNC |LOCL |0 |1 |read_sleb128
---
LLVM-gcc 4.2 on Solaris/SPARC with 64-bit long-double:
-bash-3.00$ nm unwind-dw2.o | grep read_sleb128
[613] | 144|...
2009 Oct 30
0
[LLVMdev] llvm-gcc-4.2 RELEASE_26 bootstrap failure on Solaris/SPARC - unhandled REAL_TYPE during compilation of '__powitf2'
Hello, Juergen
> Ty->dump() prints "{double, double}" in the failing case (just before my
> introduced assert).
The answer is simple. The code in question contains extended IEEE FP
argument / return type (aka 'long double'). By default it's lowered
into struct {double, double} as you already saw and sparc currently
does not provide any argument layout hooks.
There
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