Re: [PATCH 0/5] openmp: Handle pinned and unified shared memory.

2022-04-13 Thread Andrew Stubbs
This patch adjusts the testcases, previously proposed, to allow for testing on machines with varying page sizes and default amounts of lockable memory. There turns out to be more variation than I had thought. This should go on mainline at the same time as the previous patches in this thread.

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

2022-04-13 Thread Piotr Kubaj via Fortran
On 22-03-20 16:30:08, FX wrote: > Hi, > > (Please send all Fortran (front-end and libgfortran) patches in CC to the > Fortran list.) > > Please hold from pushing the patch as is, I have some questions: > > - If FreeBSD has feenableexcept() and related functions, it should already > use the fpu

[Patch] OpenMP/Fortran: Fix EXIT in loop diagnostic [PR105242]

2022-04-13 Thread Tobias Burnus
Trivial fix – after finding the issue. The LOOP directive and several LOOP/DO/SIMD combined directives were missing in the check. As the PR shows, this leads to an ICE on invalid code. OK? Tobias - Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 Mün

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

2022-04-13 Thread FX via Fortran
Hi, > the problem is that configure checks for feenableexcept() in libm: > AC_CHECK_LIB([m],[feenableexcept],[have_feenableexcept=yes > AC_DEFINE([HAVE_FEENABLEEXCEPT],[1],[libm includes feenableexcept])]) > > FreeBSD doesn't have this function in libm, it's implemented in > /usr/include/fenv.h

Re: [Patch] OpenMP/Fortran: Fix EXIT in loop diagnostic [PR105242]

2022-04-13 Thread Jakub Jelinek via Fortran
On Wed, Apr 13, 2022 at 05:16:48PM +0200, Tobias Burnus wrote: > Trivial fix – after finding the issue. The LOOP directive and > several LOOP/DO/SIMD combined directives were missing in the > check. As the PR shows, this leads to an ICE on invalid code. > > OK? > > Tobias > - > Si

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

2022-04-13 Thread Piotr Kubaj via Fortran
Hello, can you check the following patch? On 22-04-13 17:27:11, FX wrote: > Hi, > > > the problem is that configure checks for feenableexcept() in libm: > > AC_CHECK_LIB([m],[feenableexcept],[have_feenableexcept=yes > > AC_DEFINE([HAVE_FEENABLEEXCEPT],[1],[libm includes feenableexcept])]) > >