On Wed, Jan 10, 2018 at 03:19:49PM -0500, Michael Meissner wrote:
> As I add support for making -mabi=ieeelongdouble default, I noticed some
> issues
> in building libstdc++ with the default for the code that supports the
> -mlong-double-64 option. These tests add checks for -mlong-double-128 before
> considering whether TFmode/TCmode are IEEE or IBM extended double.
>
> I went into the two primary macros (FLOAT128_{IBM,IEEE}_P) and added the
> checks. I also looked at all of the TFmode/TCmode support in rs6000.c and I
> found one case where it wasn't checking the long double size first.
>
> I have done a bootstrap and regression test with this patch on a little endian
> power8 system. I previously did a bootstrap wtih the original patch (which
> includes the rs6000.h change and a similar change to rs6000.c) to add long
> double configuration and multilib on a big endian power8 system. In both
> cases, there was no regression. Can I install this patch into the trunk?
Okay. Thanks!
Segher
> 2018-01-10 Michael Meissner <meiss...@linux.vnet.ibm.com>
>
> * config/rs6000/rs6000.c (is_complex_IBM_long_double): Explicitly
> check for 128-bit long double before checking TCmode.
> * config/rs6000/rs6000.h (FLOAT128_IEEE_P): Explicitly check for
> 128-bit long doubles before checking TFmode or TCmode.
> (FLOAT128_IBM_P): Likewise.
