Displaying 4 results from an estimated 4 matches for "getifieeedoubl".
Did you mean:
getifieeedouble
2010 Jul 09
2
[LLVMdev] APFloat::convertToDouble asserts
...n is to (host) double, as the name implies. Among
> APFloat types, that is only implemented for APFloat::IEEEdouble.
>
yes, it's to host double ("convert this APFloat to double"), therefore I
hoped that it works for any APFloat type (otherwise I would suggest a
name such as getIfIEEEdouble() ).
Is there a reason against it or would it be accepted if it would work
for any type?
2010 Jul 09
2
[LLVMdev] APFloat::convertToDouble asserts
Hi!
I wonder why APFloat::convertToDouble asserts if it is not an
APFloat::IEEEdouble while the name "convertToDouble" suggests that it
converts when it is not a double.
-Jochen
2010 Jul 09
0
[LLVMdev] APFloat::convertToDouble asserts
On Jul 9, 2010, at 7:59 AMPDT, Jochen Wilhelmy wrote:
> Hi!
>
> I wonder why APFloat::convertToDouble asserts if it is not an
> APFloat::IEEEdouble while the name "convertToDouble" suggests that it
> converts when it is not a double.
The conversion is to (host) double, as the name implies. Among
APFloat types, that is only implemented for APFloat::IEEEdouble.
2010 Jul 09
0
[LLVMdev] APFloat::convertToDouble asserts
...name implies. Among
>> APFloat types, that is only implemented for APFloat::IEEEdouble.
>>
>
> yes, it's to host double ("convert this APFloat to double"),
> therefore I hoped that it works for any APFloat type (otherwise I
> would suggest a name such as getIfIEEEdouble() ).
> Is there a reason against it or would it be accepted if it would
> work for any type?
I'd rather not. The functionality you want is there, feed another
APFloat type through APFloat::convert first.
Using host FP is not something that should be encouraged; the main
point of...