On 10/30/2015 09:29 PM, Dominique d'Humières wrote:
>> diff --git a/gcc/fortran/openmp.c b/gcc/fortran/openmp.c
>
> Revision r229609 breaks bootstrap:
>
> ../../work/gcc/fortran/openmp.c: In function 'void
> resolve_omp_clauses(gfc_code*, gfc_omp_clauses*, gfc_namespace*, bool)':
>
> diff --git a/gcc/fortran/openmp.c b/gcc/fortran/openmp.c
Revision r229609 breaks bootstrap:
../../work/gcc/fortran/openmp.c: In function 'void
resolve_omp_clauses(gfc_code*, gfc_omp_clauses*, gfc_namespace*, bool)':
../../work/gcc/fortran/openmp.c:2925:27: error: format '%L' expects argument
On Thu, Oct 22, 2015 at 08:21:35AM -0700, Cesar Philippidis wrote:
> diff --git a/gcc/fortran/gfortran.h b/gcc/fortran/gfortran.h
> index b2894cc..93adb7b 100644
> --- a/gcc/fortran/gfortran.h
> +++ b/gcc/fortran/gfortran.h
> @@ -1123,6 +1123,7 @@ typedef struct gfc_omp_namelist
> } u;
>
On 10/30/2015 07:47 AM, Jakub Jelinek wrote:
> On Thu, Oct 22, 2015 at 08:21:35AM -0700, Cesar Philippidis wrote:
>> diff --git a/gcc/fortran/gfortran.h b/gcc/fortran/gfortran.h
>> index b2894cc..93adb7b 100644
>> --- a/gcc/fortran/gfortran.h
>> +++ b/gcc/fortran/gfortran.h
>> @@ -1123,6 +1123,7
On Fri, Oct 30, 2015 at 08:02:12AM -0700, Cesar Philippidis wrote:
> On 10/30/2015 07:47 AM, Jakub Jelinek wrote:
> > On Thu, Oct 22, 2015 at 08:21:35AM -0700, Cesar Philippidis wrote:
> >> diff --git a/gcc/fortran/gfortran.h b/gcc/fortran/gfortran.h
> >> index b2894cc..93adb7b 100644
> >> ---
On 10/30/2015 09:58 AM, Jakub Jelinek wrote:
> What I meant not just the above changes, but also all changes that
> replace where with >where and the like, so pretty much everything
> except for the oacc_compatible_clauses removal and addition of
> resolve_omp_duplicate_list. That is kind of
Hi!
On Fri, Oct 30, 2015 at 10:03:23AM -0700, Cesar Philippidis wrote:
This looks good to me, iff you write ChangeLog entry for it.
> diff --git a/gcc/fortran/gfortran.h b/gcc/fortran/gfortran.h
> index 90f63cf..13e730f 100644
> --- a/gcc/fortran/gfortran.h
> +++ b/gcc/fortran/gfortran.h
> @@
Currently, for certain omp and oacc errors the fortran will inaccurately
report exactly where in the omp/acc construct the error has occurred. E.g.
!$acc parallel copy (i) copy (i) copy (j)
1
Error: Symbol ‘i’ present on multiple clauses at (1)
