Re: [PATCH] fortran, libgfortran, v3: Avoid using libquadmath for glibc 2.26+

2022-06-28 Thread Jakub Jelinek via Gcc-patches
On Tue, Jun 28, 2022 at 10:35:03AM +0200, Tobias Burnus wrote: > On 27.06.22 15:30, Jakub Jelinek via Gcc-patches wrote: > > > Ok, here is an updated patch that uses _Float128/_Complex _Float128 for all > > of GFC_REAL_{16,17}_IS_FLOAT128, but still uses q/Q suffixes on literal > > constants etc.

Re: [PATCH] fortran, libgfortran, v3: Avoid using libquadmath for glibc 2.26+

2022-06-28 Thread Tobias Burnus
On 27.06.22 15:30, Jakub Jelinek via Gcc-patches wrote: Ok, here is an updated patch that uses _Float128/_Complex _Float128 for all of GFC_REAL_{16,17}_IS_FLOAT128, but still uses q/Q suffixes on literal constants etc. when using libquadmath and f128/F128 otherwise. This patch also includes the

Re: [PATCH] fortran, libgfortran, v3: Avoid using libquadmath for glibc 2.26+

2022-06-28 Thread Jakub Jelinek via Gcc-patches
On Mon, Jun 27, 2022 at 03:30:49PM +0200, Jakub Jelinek via Gcc-patches wrote: > Ok, here is an updated patch that uses _Float128/_Complex _Float128 for all > of GFC_REAL_{16,17}_IS_FLOAT128, but still uses q/Q suffixes on literal > constants etc. when using libquadmath and f128/F128 otherwise. > T

[PATCH] fortran, libgfortran, v3: Avoid using libquadmath for glibc 2.26+

2022-06-27 Thread Jakub Jelinek via Gcc-patches
On Mon, Jun 27, 2022 at 01:56:10PM +0200, Mikael Morin wrote: > Le 27/06/2022 à 09:54, Jakub Jelinek a écrit : > > Still, using __float128 when the APIs are declared for __float128 and > > _Float128 when the APIs are declared for _Float128 can be better for > > consistency. > > > I agree with that