On Fri, 13 Aug 2021, Andreas Schwab wrote: > On Aug 12 2021, Patrick McGehearty via Gcc-patches wrote: > > > diff --git a/libgcc/config/rs6000/_divkc3.c b/libgcc/config/rs6000/_divkc3.c > > index a1d29d2..2b229c8 100644 > > --- a/libgcc/config/rs6000/_divkc3.c > > +++ b/libgcc/config/rs6000/_divkc3.c > > @@ -38,10 +38,10 @@ see the files COPYING3 and COPYING.RUNTIME > > respectively. If not, see > > #endif > > > > #ifndef __LONG_DOUBLE_IEEE128__ > > -#define RBIG (__LIBGCC_KF_MAX__ / 2) > > -#define RMIN (__LIBGCC_KF_MIN__) > > -#define RMIN2 (__LIBGCC_KF_EPSILON__) > > -#define RMINSCAL (1 / __LIBGCC_KF_EPSILON__) > > +#define RBIG (__LIBGCC_DF_MAX__ / 2) > > +#define RMIN (__LIBGCC_DF_MIN__) > > +#define RMIN2 (__LIBGCC_DF_EPSILON__) > > +#define RMINSCAL (1 / __LIBGCC_DF_EPSILON__) > > How can it happen that __LONG_DOUBLE_IEEE128__ is not defined? This > file is always compiled with -mfloat128 and this looks like dead code.
I think the answer there is that -mfloat128 serves to enable __float128, it doesn't change the long double ABI, which is what __LONG_DOUBLE_IEEE128__ refers to (that's what -mabi=ieeelongdouble does). -- Joseph S. Myers jos...@codesourcery.com
