On Wed, 15 Jun 2016, Michael Meissner wrote: > Note, I do feel the front ends should be modified to allow __complex > __float128 > directly rather than having to use an attribute to force the complex type (and > to use mode(TF) on x86 or mode(KF) on PowerPC). It would clean up both x86 > and > PowerPC. However, those patches aren't written yet.
I'm now working on support for TS 18661-3 _FloatN / _FloatNx type names (keywords), constant suffixes and <float.h> addiitions. That will address, for C, the need to use modes for complex float128 (bug 32187) by allowing the standard _Complex _Float128 to be used. The issue would still apply for C++ (I'm not including any C++ support for these type names / constant suffixes in my patch), and for complex ibm128. -- Joseph S. Myers jos...@codesourcery.com
