Use existing middle end checking for Fortran OpenACC loop clauses

[Thomas Schwinge]

Hi!

On 2018-12-09T13:58:51+0100, I wrote:
> Committed to trunk in r266922:

>     Use existing middle end checking for Fortran OpenACC loop clauses
>
>     Don't duplicate in the Fortran front end what's generically being checked in
>     the middle end.
>
>             gcc/fortran/
>             * openmp.c (resolve_oacc_loop_blocks): Remove checking of OpenACC
>             loop clauses.
>             gcc/testsuite/
>             * gfortran.dg/goacc/loop-2-kernels.f95: Update.
>             * gfortran.dg/goacc/loop-2-parallel.f95: Likewise.
>             * gfortran.dg/goacc/nested-parallelism.f90: Likewise.

Similar to that, I've noticed inconsistent diagnostics in C/C++ vs.
Fortran for OpenACC 'loop' clauses with arguments only allowed inside
OpenACC 'kernels' regions, so I pushed "[Fortran] Remove OpenACC 'loop'
inside 'parallel' special-case code" to master branch in commit
4c27f900950ed0ecb2897a8931c5cc348b1980be, and backported to
releases/gcc-10 in commit f41ca73aa11f28ad7d847ac5bf7e07f8bc763721, see
attached.


Grüße
 Thomas


-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander Walter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Fortran-Remove-OpenACC-loop-inside-parallel-special-.patch
Type: text/x-diff
Size: 5016 bytes
Desc: not available
URL: <https://gcc.gnu.org/pipermail/fortran/attachments/20201106/2c47eff2/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Fortran-Remove-OpenACC-loop-inside-parallel-spec.g10.patch
Type: text/x-diff
Size: 5086 bytes
Desc: not available
URL: <https://gcc.gnu.org/pipermail/fortran/attachments/20201106/2c47eff2/attachment-0003.bin>