On Thu, Jun 16, 2016 at 10:06:48PM +0000, Joseph Myers wrote: > 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.
Great! Of course we will need to have some solution for C++. And we will have to live with the current stuff in GCC 6.x. -- Michael Meissner, IBM IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA email: meiss...@linux.vnet.ibm.com, phone: +1 (978) 899-4797