Re: libgfortran.so SONAME and powerpc64le-linux ABI changes

2021-10-05 Thread Segher Boessenkool
Hi! On Tue, Oct 05, 2021 at 10:16:47PM +0200, Thomas Koenig wrote: > On 04.10.21 16:14, Jakub Jelinek via Fortran wrote: > >Based on some IRC discussion, yet another option would be bump libgfortran > >SONAME (on all arches), make real(kind=16) on powerpc64le-linux mean > >always IEEE quad (starti

Re: libgfortran.so SONAME and powerpc64le-linux ABI changes

2021-10-05 Thread Jonathan Wakely via Fortran
On Mon, 4 Oct 2021, 15:14 Jakub Jelinek via Gcc, wrote: > On Mon, Oct 04, 2021 at 12:07:54PM +0200, Jakub Jelinek via Gcc wrote: > > Or the last option would be to try to make libgfortran.so.5 ABI > compatible > > with both choices on powerpc64le-linux. From quick skimming of > libgfortran, > >

Re: libgfortran.so SONAME and powerpc64le-linux ABI changes

2021-10-05 Thread Thomas Koenig via Fortran
On 04.10.21 16:14, Jakub Jelinek via Fortran wrote: Based on some IRC discussion, yet another option would be bump libgfortran SONAME (on all arches), make real(kind=16) on powerpc64le-linux mean always IEEE quad (starting with GCC 12) and if wanted add support for real(kind=15) meaning double

Re: [Patch] Fortran: Fix deprecate warning with parameter

2021-10-05 Thread Tobias Burnus
Hi Harald, On 05.10.21 21:10, Harald Anlauf wrote: Am 05.10.21 um 20:03 schrieb Tobias Burnus: Played around with the warning in the 'omp_lib' module (needs tweaking as for the current version, no warning is done). Turned out that already use omp_lib outputs a warning even when not used. t

Re: [Patch] Fortran: Fix deprecate warning with parameter

2021-10-05 Thread Harald Anlauf via Fortran
Hi Tobias, Am 05.10.21 um 20:03 schrieb Tobias Burnus: Played around with the warning in the 'omp_lib' module (needs tweaking as for the current version, no warning is done). Turned out that already   use omp_lib outputs a warning even when not used. that must have been a non-trivial example;

[Patch] Fortran: Fix deprecate warning with parameter

2021-10-05 Thread Tobias Burnus
Played around with the warning in the 'omp_lib' module (needs tweaking as for the current version, no warning is done). Turned out that already use omp_lib outputs a warning even when not used. That's fixed by the attached patch - even if the location is not perfect. OK for GCC 12 + GCC 11 bac

Re: libgfortran.so SONAME and powerpc64le-linux ABI changes

2021-10-05 Thread Segher Boessenkool
Hi Joseph, On Mon, Oct 04, 2021 at 07:24:31PM +, Joseph Myers wrote: > On Mon, 4 Oct 2021, Segher Boessenkool wrote: > > Some current Power GCC targets support neither. Some support only > > double-double. Making IEEE QP float work on those (that is, those that > > are < power8) will require

Possible bug: array-coarray of derived type with allocatable component

2021-10-05 Thread Harris Snyder
Hi everyone, The following program produces incorrect results (GCC 11.2.0, OpenCoarrays 2.9.2). The line marked `! NOTE` should print 1, 2, 3, 4, but instead I get "OpenCoarrays internal error on image 2: libcaf_mpi::caf_sendget_by_ref(): can not allocate 0 bytes of memory." This may be an OpenCo

[committed] gfortran.dg/gomp/pr43711.f90: Change dg-* for XFAIL->PASS

2021-10-05 Thread Tobias Burnus
Adapt testcase to better catch the current message and expected follow-up messages + use the proper dg-*. — Result: XFAIL changed to PASS. Committed as r12-4185. Probably some other testcases could be checked as well. Maybe we also find some real & unfixed bugs that way. Tobias ---