------- Comment #8 from ktietz at gcc dot gnu dot org 2009-09-27 09:28 ------- (In reply to comment #7) > The new attribute "basetype_mode" (see > http://gcc.gnu.org/ml/gcc-patches/2009-09/msg01907.html for patch) could > provide a way to solve this, as it makes sure that it is associated to the > base > type, instead of the current type declaration as "mode" attribute does. > > by defining __float128 as '#define __float128 float __attribute__ > ((basetype_mode(DF)))' > > Constructs like '__complex__ DFtype z;' getting handled proper, too. Err, I meant here of course '__complex__ __float128 z;'
> Maybe this is a way to solve this issue. > > Kai > -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32187
