Re: [PATCH] Handle "omp simd array" accesses in ifcvt_memrefs_wont_trap

2019-05-31 Thread Richard Biener
On Fri, 31 May 2019, Jakub Jelinek wrote: > On Fri, May 31, 2019 at 11:43:29AM +0200, Richard Biener wrote: > > Hmm. Is it enough to set TREE_THIS_NOTRAP on the ARRAY_REF instead? > > That works too. > > > At least it's documented the ARRAY_REF then isn't the issue. > > As for conditional vs. u

Re: [PATCH] Handle "omp simd array" accesses in ifcvt_memrefs_wont_trap

2019-05-31 Thread Jakub Jelinek
On Fri, May 31, 2019 at 11:43:29AM +0200, Richard Biener wrote: > Hmm. Is it enough to set TREE_THIS_NOTRAP on the ARRAY_REF instead? That works too. > At least it's documented the ARRAY_REF then isn't the issue. > As for conditional vs. unconditional I'm not so sure but automatic > vars are exc

Re: [PATCH] Handle "omp simd array" accesses in ifcvt_memrefs_wont_trap

2019-05-31 Thread Richard Biener
On Fri, 31 May 2019, Jakub Jelinek wrote: > Hi! > > As a preparation for lastprivate(conditional:) on #pragma omp simd, I need > if-conversion to handle "omp simd array" accesses. These are safe, no > matter whether written or read, each simd lane accesses their own element, > after the vectoriz

[PATCH] Handle "omp simd array" accesses in ifcvt_memrefs_wont_trap

2019-05-31 Thread Jakub Jelinek
Hi! As a preparation for lastprivate(conditional:) on #pragma omp simd, I need if-conversion to handle "omp simd array" accesses. These are safe, no matter whether written or read, each simd lane accesses their own element, after the vectorization it is all just a single vector read or store or R