Is the use of FRACTIONAL_FLOAT_MODE to avoid iterations over floating-point modes including these modes when they shouldn't, as discussed previously?
If so, how do you deal (in subsequent patches?) with iterations that *should* include these modes? In particular, where libgcc uses __LIBGCC_<mode>_* macros predefined with -fbuilding-libgcc in an interation in c-cppbuiltin.c, how do you handle getting the relevant information in libgcc to build applicable libgcc functions for these modes? (I'm presuming that you do want complex arithmetic to work for both 128-bit types, for example, although you won't want them to be used for intermediate conversions in libgcc operations on other types.) -- Joseph S. Myers jos...@codesourcery.com
