[og12] OpenACC: Don't gang-privatize artificial variables: restrict to blocks (was: [PATCH] [og12] OpenACC: Don't gang-privatize artificial variables)

Hi! On 2022-10-18T15:59:24+0100, Julian Brown wrote: > On Tue, 18 Oct 2022 16:46:07 +0200 Thomas Schwinge > wrote: >> On 2022-10-14T13:38:56+, Julian Brown wrote: >> ..., but to my surprised, that did fire in one occasion: >> >> > --- a/libgomp/testsuite/libgomp.oacc-fortran/privatized-ref

Re: [og12] OpenACC: Don't gang-privatize artificial variables: restrict to blocks (was: [PATCH] [og12] OpenACC: Don't gang-privatize artificial variables)

Hi! On 2022-10-28T10:11:04+0200, I wrote: > On 2022-10-18T15:59:24+0100, Julian Brown wrote: >> On Tue, 18 Oct 2022 16:46:07 +0200 Thomas Schwinge >> wrote: >>> On 2022-10-14T13:38:56+, Julian Brown wrote: >>> ..., but to my surprised, that did fire in one occasion: >>> >>> > --- a/libgomp

OpenACC: Don't gang-privatize artificial variables [PR90115] (was: [PATCH] [og12] OpenACC: Don't gang-privatize artificial variables)

Hi! On 2022-10-18T16:46:07+0200, Thomas Schwinge wrote: > On 2022-10-14T13:38:56+, Julian Brown wrote: >> This patch prevents compiler-generated artificial variables from being >> treated as privatization candidates for OpenACC. >> >> The rationale is that e.g. "gang-private" variables actua

Re: [PATCH v2 1/3] libcpp: reject codepoints above 0x10FFFF

On Thu, 2022-10-27 at 19:16 -0400, Ben Boeckel wrote: > Unicode does not support such values because they are unrepresentable > in > UTF-16. Wikipedia pointed me to RFC 3629, which was when UTF-8 introduced this restriction, whereas libcpp was implementing the higher upper limit from the earlier,

Re: [PATCH v2 2/3] libcpp: add a function to determine UTF-8 validity of a C string

On Thu, 2022-10-27 at 19:16 -0400, Ben Boeckel wrote: > This simplifies the interface for other UTF-8 validity detections > when a > simple "yes" or "no" answer is sufficient. > > Signed-off-by: Ben Boeckel > --- >  libcpp/ChangeLog  |  6 ++ >  libcpp/charset.cc | 18 ++ >  lib

adding attributes

Assuming there's no technical reason not to, can someone say what would be involved in adding relevant attributes (at least function ones) like those for C? I'm thinking particularly of target_clones, but others probably make sense. I don't know my way around, but I had a quick look, and it at le

Re: [PATCH v2 2/3] libcpp: add a function to determine UTF-8 validity of a C string

On Fri, Oct 28, 2022 at 08:59:16 -0400, David Malcolm wrote: > On Thu, 2022-10-27 at 19:16 -0400, Ben Boeckel wrote: > > This simplifies the interface for other UTF-8 validity detections > > when a > > simple "yes" or "no" answer is sufficient. > > > > Signed-off-by: Ben Boeckel > > --- > >  libc

Re: [PATCH v2 3/3] p1689r5: initial support

On Thu, Oct 27, 2022 at 19:16:44 -0400, Ben Boeckel wrote: > diff --git a/gcc/testsuite/g++.dg/modules/modules.exp > b/gcc/testsuite/g++.dg/modules/modules.exp > index afb323d0efd..7fe8825144f 100644 > --- a/gcc/testsuite/g++.dg/modules/modules.exp > +++ b/gcc/testsuite/g++.dg/modules/modules.exp

[PATCH] Fortran: ordering of hidden procedure arguments [PR107441]

Dear all, the passing of procedure arguments in Fortran sometimes requires ancillary parameters that are "hidden". Examples are string length and the presence status of scalar variables with optional+value attribute. The gfortran ABI is actually documented: https://gcc.gnu.org/onlinedocs/gfortr