On Tue, Sep 06, 2022 at 07:54:05AM +0800, haochen.jiang via Gcc-patches wrote:
> On Linux/x86_64,
>
> 938cda536019cd6a1bc0dd2346381185b420bbf8 is the first bad commit
> commit 938cda536019cd6a1bc0dd2346381185b420bbf8
> Author: Tobias Burnus <tob...@codesourcery.com>
> Date: Mon Sep 5 18:05:24 2022 +0200
>
> Fortran/openmp: Partial OpenMP 5.2 doacross and omp_cur_iteration support
>
> caused
>
> FAIL: gfortran.dg/gomp/doacross-5.f90 -O (test for errors, line 28)
> FAIL: gfortran.dg/gomp/doacross-5.f90 -O (test for errors, line 42)
> FAIL: gfortran.dg/gomp/doacross-5.f90 -O (test for errors, line 48)
> FAIL: gfortran.dg/gomp/doacross-5.f90 -O (test for errors, line 55)
> FAIL: gfortran.dg/gomp/doacross-5.f90 -O (test for errors, line 70)
> FAIL: gfortran.dg/gomp/doacross-5.f90 -O (test for errors, line 82)
> FAIL: gfortran.dg/gomp/doacross-5.f90 -O (test for excess errors)
Seems this is still being diagnosed in the FE when it should be deferred to
the middle-end now (only when we find out if it is doacross or not).
If you really want to diagnose it in the FE (and do the doacross discovery
there too), I think the testcase needs to be split into 2, because the FE
errors apparently result in the gimplifier or omp lowering not being done
at all.
Jakub
