On Mon, Jun 18, 2018 at 03:34:37PM -0400, Michael Meissner wrote: > This is just the combined patch of the last three patches that have been > approved for trunk. I expanded the description in rs6000-modes.def of what > the > 3 128-bit floating point types are and why IFmode needs to be ordered above > KFmode and TFmode. > > These patches were individually proposed in: > https://gcc.gnu.org/ml/gcc-patches/2018-06/msg00634.html > https://gcc.gnu.org/ml/gcc-patches/2018-06/msg00796.html > https://gcc.gnu.org/ml/gcc-patches/2018-06/msg00799.html > > In terms of the tests, the following tests fail if you switch the default long > double format. At the moment, I don't have the GLIBC that provides native > support for IEEE 128-bit long double:
<snip> Is this a regression, or do those failures happen on trunk with default ieee128 long double already? Segher
