Re: [PATCH] fortran: use fpu-glibc on powerpc*-unknown-freebsd

2022-04-28 Thread FX via Fortran
> Given that 12 has been branched off, is it OK now to commit this patch? How does the patch affect the results of “make check-gfortran”? How many tests that failed or were unsupported pass? FX

Re: [patch, fortran, doc] Mention new CONVERT options for POWER

2022-04-28 Thread Bernhard Reutner-Fischer via Fortran
Hi Thomas, On 27 April 2022 22:34:39 CEST, Thomas Koenig via Fortran wrote: +@item @code{'big_endian'} Do all unformatted I/O in big_endian mod.e ISTM that this should be s/mod.e/mode./ ? thanks,

Re: [PATCH] fortran: use fpu-glibc on powerpc*-unknown-freebsd

2022-04-28 Thread Piotr Kubaj via Fortran
Given that 12 has been branched off, is it OK now to commit this patch? On 22-04-14 16:09:35, Piotr Kubaj wrote: > On 22-04-14 09:05:17, FX wrote: > > Hi, > > > > > can you check the following patch? > > > > Why restrict it to powerpc-freebsd only, and not all freebsd? Do they > > differ? > amd

[patch, wwwdocs] Mention POWER IEEE128 changes for gcc 12

2022-04-28 Thread Thomas Koenig via Fortran
Hi, the attached patch documents the support for IEEE long double for Fortran. OK? Suggestions for better wording? Best regards Thomas Mention support for IEEE 128-bit long double for Fortran. * htdocs/gcc-12/changes.html: Mention support for IEEE 128-bit long doubl

Re: [patch, fortran, doc] Mention new CONVERT options for POWER

2022-04-28 Thread Richard Biener via Fortran
On Wed, Apr 27, 2022 at 10:34 PM Thomas Koenig via Fortran wrote: > > Hi, > > as we say in German "Nicht documentiert ist nicht gemacht", if > it is not documented, it wasn't done. > > So I thought it would be time to document the changes to the various > ways of specifying CONVERT before gcc12 we