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 a
On Mon, 18 Jun 2018, Michael Meissner wrote:
> In terms of the tests, the following tests fail if you switch the default long
> double format.
Also, having done a test build: various *tf* and *tc* libgcc functions end
up getting built incorrectly (to use IEEE long double when the ABIs for
those
On Mon, Jun 18, 2018 at 07:40:46PM +, Joseph Myers wrote:
> On Mon, 18 Jun 2018, Michael Meissner wrote:
>
> > gcc.target/powerpc/pr70117.c(bug in isnormal on
> > IEEE 128)
>
> Doesn't look like a bug in isnormal to me. That test is explicitly using
> an IBM long do
On Mon, 18 Jun 2018, Michael Meissner wrote:
> gcc.target/powerpc/pr70117.c (bug in isnormal on IEEE 128)
Doesn't look like a bug in isnormal to me. That test is explicitly using
an IBM long double representation and can't possibly be expected to work
with IEEE long double - e
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
