On Thu, Aug 12, 2021 at 04:47:42PM +0000, Joseph Myers wrote: > On Thu, 12 Aug 2021, Patrick McGehearty via Gcc-patches wrote: > > My understanding of ibm FP mode build procedure is minimal, > > but it seems that the _divkc3.c routine is built for both IEEE128 > > and IBM128 modes. > > If built for IBM128 mode (i.e., compiler defaults to TFmode = IBM long > double), it should still build a function __divkc3 which takes IEEE > binary128 arguments and uses IEEE binary128 (KFmode) constants.
Apparently that is broken then :-( > If you were changing the L_divtc3 case in libgcc2.c to use different > constants in the case where TFmode is IBM long double, that would make > sense to me. This whole thing is there to *not* change generic code. Segher
