http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51057
--- Comment #2 from Iain Sandoe <iains at gcc dot gnu.org> 2011-12-03 20:36:43 UTC --- whilst I appreciate that there are wider issues with IBM long double (and its availability) [I read the two PRs you cross-referenced]. In this case, it appears to be a different situation. - what Dominique is indicating is that the tests are likely failing on an IBM long double target because the number of mantissa bits is 106 rather than the 112 for float128. So I wonder what opportunities exist for adjusting the test expectation depending on the target. (since this, presumably, will affect all IBM long double targets). from 'c' we have some #defines that would allow us to detect the IBM case on ppc (although, presumably because it's provided by a library, we don't get the same for x86). It would even be a reasonable first approximation to assume IBM long double on ppc and float128 on x86. --- This would allow some kind of target capability test in tcl - which could thence regulate some conditional compilation of the Fortran, I guess? I assume the Fortran can't see the 'c' defines (ISTR a PR about that somewhen).
