Displaying 4 results from an estimated 4 matches for "floattobits".
2007 Oct 19
3
[LLVMdev] troubles with llvm-gcc 4.0 and APFloat on X86_64
...are not converted correctly
to the particular target format (double precision works as expected).
it seems the problem is related to the following piece of code taken
from APFloat.cpp:1836 (called from ConvertREAL_CST)
APFloat::APFloat(float f) {
APInt api = APInt(32, 0);
initFromAPInt(api.floatToBits(f));
}
i guess the floatToBits call will return the wrong half word since ints
are 4, but float and double are both 8 byte on x86_64 (but i'm not yet
sure).
is anybody having the same kind of problems or is there an official
patch for this issue? is llvm-gcc known to work as a cross compi...
2007 Oct 19
0
[LLVMdev] troubles with llvm-gcc 4.0 and APFloat on X86_64
...produces an invalid constant in the .ll file? Can you give an example?
> it seems the problem is related to the following piece of code taken
> from APFloat.cpp:1836 (called from ConvertREAL_CST)
> APFloat::APFloat(float f) {
> APInt api = APInt(32, 0);
> initFromAPInt(api.floatToBits(f));
> }
>
> i guess the floatToBits call will return the wrong half word since
> ints
> are 4, but float and double are both 8 byte on x86_64 (but i'm not yet
> sure).
I'm pretty sure float is 4 everywhere; that wouldn't be it.
> is anybody having the same kin...
2007 Oct 20
2
[LLVMdev] troubles with llvm-gcc 4.0 and APFloat on X86_64
...w) to link the ieee754 softfloat
library into libgcc.
>> it seems the problem is related to the following piece of code taken
>> from APFloat.cpp:1836 (called from ConvertREAL_CST)
>> APFloat::APFloat(float f) {
>> APInt api = APInt(32, 0);
>> initFromAPInt(api.floatToBits(f));
>> }
>>
>> i guess the floatToBits call will return the wrong half word since
>> ints
>> are 4, but float and double are both 8 byte on x86_64 (but i'm not yet
>> sure).
>
> I'm pretty sure float is 4 everywhere; that wouldn't be it.
su...
2007 Oct 22
0
[LLVMdev] troubles with llvm-gcc 4.0 and APFloat on X86_64
...at
> library into libgcc.
>
>>> it seems the problem is related to the following piece of code taken
>>> from APFloat.cpp:1836 (called from ConvertREAL_CST)
>>> APFloat::APFloat(float f) {
>>> APInt api = APInt(32, 0);
>>> initFromAPInt(api.floatToBits(f));
>>> }
>>>
>>> i guess the floatToBits call will return the wrong half word since
>>> ints
>>> are 4, but float and double are both 8 byte on x86_64 (but i'm not yet
>>> sure).
>> I'm pretty sure float is 4 everywhere; that...