Hi!
On Tue, Nov 03, 2020 at 10:25:05PM -0500, Michael Meissner wrote:
> On Sat, Oct 31, 2020 at 11:39:23PM +1030, Alan Modra wrote:
> > Why is this is wrong? If you are configuring using
> > --without-long-double-128 then that doesn't mean 128-bit long doubles
> > are unsupported, it just selects
On Sat, Oct 31, 2020 at 11:39:23PM +1030, Alan Modra wrote:
> Hi Mike,
> On Wed, Oct 28, 2020 at 08:42:04PM -0400, Michael Meissner via Gcc-patches
> wrote:
> > PowerPC: PR libgcc/97543, fix 64-bit long double issues
> >
> > There are two issues in PR libgcc/97543 which shows up if you build a GC
Self-ping.
Mike, can you reply to Alan's mail please? He makes a lot of points,
not all of them bad certainly!
Segher
On Wed, Oct 28, 2020 at 08:42:04PM -0400, Michael Meissner wrote:
> PowerPC: PR libgcc/97543, fix 64-bit long double issues
>
> There are two issues in PR libgcc/97543 which
Hi Mike,
On Wed, Oct 28, 2020 at 08:42:04PM -0400, Michael Meissner via Gcc-patches
wrote:
> PowerPC: PR libgcc/97543, fix 64-bit long double issues
>
> There are two issues in PR libgcc/97543 which shows up if you build a GCC
> compiler with long double defaulting to 64-bit instead of 128-bit wi
PowerPC: PR libgcc/97543, fix 64-bit long double issues
There are two issues in PR libgcc/97543 which shows up if you build a GCC
compiler with long double defaulting to 64-bit instead of 128-bit with IBM
extended double:
1) The first issue was the t-linux file forced the entire libgcc libra
