Re: [gomp4] don't error on implicitly private induction variables in gfortran

2017-01-27 Thread Cesar Philippidis
On 01/27/2017 07:07 AM, Jakub Jelinek wrote: > On Fri, Jan 27, 2017 at 07:02:45AM -0800, Cesar Philippidis wrote: >> diff --git a/gcc/fortran/openmp.c b/gcc/fortran/openmp.c >> index 61940d7..2782a8d 100644 >> --- a/gcc/fortran/openmp.c >> +++ b/gcc/fortran/openmp.c >> @@ -5192,7 +5192,8 @@ gfc_re

Re: [gomp4] don't error on implicitly private induction variables in gfortran

2017-01-27 Thread Jakub Jelinek
On Fri, Jan 27, 2017 at 07:02:45AM -0800, Cesar Philippidis wrote: > While experimenting with some new OpenACC benchmarks, I noticed that > gfortran errors when the user explicitly marks loop induction variables > as private. I applied this patch to gomp-4_0-branch to resolve that problem. > > Ces

[gomp4] don't error on implicitly private induction variables in gfortran

2017-01-27 Thread Cesar Philippidis
While experimenting with some new OpenACC benchmarks, I noticed that gfortran errors when the user explicitly marks loop induction variables as private. I applied this patch to gomp-4_0-branch to resolve that problem. Cesar 2017-01-26 Cesar Philippidis gcc/fortran/ * openmp.c (gfc_resolve_oa