Re: [boost] [math] Support for libquadmath/ __float128

Subject: Re: [boost] [math] Support for libquadmath/ __float128
From: Claas H. Köhler (claas.koehler_at_[hidden])
Date: 2013-02-25 05:35:01

On 25/02/13 11:16, Paul A. Bristow wrote:
>> -----Original Message-----
>> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of John Maddock
>> Sent: Monday, February 25, 2013 9:22 AM
>> To: boost_at_[hidden]
>> Subject: Re: [boost] [math] Support for libquadmath/ __float128
>>
>>> So this means that the suffixes L and l are the "longest"
>>> floating-point suffixes supported by the language and that the
>>> suffixes Q and q are non-portable language extensions. Is this right?
>>
>> Correct.
>>
>>> So the only way to add Q or q suffixes would be to find a way to query
>>> the environment if it is supported. I wonder if GCC with
>>> --enable-libquadmath has a kind of query for this.
>>
>> I haven't found one - gcc-4.7.2 has all sorts of __SIZEOF_XXX__ defines for every last type
> *except*
>> __float128 and __float80 :-(
>
Sorry for a possibly stupid questio, but is it not possible to use any 
of the FLT128_XXX defines listed here:

http://gcc.gnu.org/onlinedocs/libquadmath/Typedef-and-constants.html#Typedef-and-constants

Claas

> It won't help now, but is 'more precise types' an issue to raise with WG21 for the next C++
> standard?
>
> Or is Multiprecision the way to go?
>
> Paul
>
>
>
>
>
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
>