Thanks Thomas, pushed as 228173565eafbe34e44c1600c32e32a323eb5aab
228173565eafbe34e44c1600c32e32a323eb5aab.patch
Description: Binary data
Hi FX,
I’m not opposed, but I’d really like to get this into the current branch. It is
a much less invasive change than the power-ieee128 work. The only case I
changed is the case where there is a kind 16, and there is a long double, but
the long double is neither kind 10 neither kind 16. I
Hi Thomas,
> I am not sure the logic is correct for POWER (old style) where we have
> a 16-byte long double made up from two 8-byte doubles, which is not
> __float128 (IFmode)
As written, the patch should be a no-op for existing platforms. I know about
the ppc double-double "long double" type, a
Hi FX,
I am not sure the logic is correct for POWER (old style) where we have
a 16-byte long double made up from two 8-byte doubles, which is not
__float128 (IFmode), see
https://gcc.gnu.org/pipermail/fortran/2021-November/056912.html
I have a proposal: Since I am currently trying to unravel th
A gentle ping…
> Le 7 déc. 2021 à 15:11, FX a écrit :
>
> Hi,
>
> Right now, the logic in libgfortran for the detection of REAL(KIND=16) is in
> kinds-override.h:
>
> /* What are the C types corresponding to the real(kind=10) and
> real(kind=16) types? We currently rely on the following as
Hi,
Right now, the logic in libgfortran for the detection of REAL(KIND=16) is in
kinds-override.h:
/* What are the C types corresponding to the real(kind=10) and
real(kind=16) types? We currently rely on the following assumptions:
-- if real(kind=10) exists, i.e. if HAVE_GFC_REAL_10 is d
