Re: Don't create location wrapper nodes within OpenACC clauses (was: [WIP] Fold 'NON_LVALUE_EXPR' some more (was: C++ 'NON_LVALUE_EXPR' in OMP array section handling))

On Thu, Nov 26, 2020 at 10:36:43AM +0100, Thomas Schwinge wrote: > So, I understand, 'NON_LVALUE_EXPR's are primarily a C/C++ (only?) front > end construct to wrap nodes that must not be used as a lvalue (per the > programming language standards); rejecting code like 'int x; &(x + 0);', > I suppose

[WIP] Fold 'NON_LVALUE_EXPR' some more (was: C++ 'NON_LVALUE_EXPR' in OMP array section handling)

Hi! Anyone have any input here, especially whether something like the WIP patch attached to generally "Fold 'NON_LVALUE_EXPR' some more" is preferable over local 'STRIP_NOPS'? On 2020-03-26T20:53:19+0100, I wrote: > On 2020-03-26T09:09:01-0600, Sandra Loosemore wrote: >> On 3/26/20 8:27 AM, Thom

Re: C++ 'NON_LVALUE_EXPR' in OMP array section handling

Hi! On 2020-03-26T09:09:01-0600, Sandra Loosemore wrote: > On 3/26/20 8:27 AM, Thomas Schwinge wrote: >> Note that as this code is shared between OpenACC/OpenMP, this might >> affect OpenMP, too, as far as I can tell. (Subject updated.) Jakub, can >> you please have a look, too? >> >> On 2020-0

Re: C++ 'NON_LVALUE_EXPR' in OMP array section handling

On 3/26/20 8:27 AM, Thomas Schwinge wrote: Hi! Note that as this code is shared between OpenACC/OpenMP, this might affect OpenMP, too, as far as I can tell. (Subject updated.) Jakub, can you please have a look, too? On 2020-03-25T23:02:38-0600, Sandra Loosemore wrote: The attached patch fix

C++ 'NON_LVALUE_EXPR' in OMP array section handling (was: [PATCH, OpenACC] Bug fix for processing OpenACC data clauses in C++)

Hi! Note that as this code is shared between OpenACC/OpenMP, this might affect OpenMP, too, as far as I can tell. (Subject updated.) Jakub, can you please have a look, too? On 2020-03-25T23:02:38-0600, Sandra Loosemore wrote: > The attached patch fixes a bug I found in the C++ front end's hand