[Bug fortran/98014] New: [Fortran OpenACC] Empty '!$acc' continuation line rejected

[tschwinge at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98014

            Bug ID: 98014
           Summary: [Fortran OpenACC] Empty '!$acc' continuation line
                    rejected
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Keywords: openacc
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tschwinge at gcc dot gnu.org
                CC: burnus at gcc dot gnu.org, jakub at gcc dot gnu.org
  Target Milestone: ---

A while ago, I noticed that given an empty '!$acc' continuation line:

    !$acc parallel &
    !$acc   vector_length (1) &
    !$acc ! { dg-warning "using vector_length \\(32\\), ignoring 1" "" { target
openacc_nvidia_accel_selected } }

..., GCC doesn't like that:

    [...]: Error: Failed to match clause at (1)

If I remember correctly (haven't verified now), same thing if placing a
continuation '&' after the sentinel '!$acc'.

If I remember correctly (haven't verified now), we do accept all this for the
corresponding OpenMP constructs, and it is legal for OpenACC and OpenMP.


Is that maybe related to PR98011 "[OpenACC] 'gcc/fortran/scanner.c:load_line'
should consider 'flag_openacc' in addition to 'flag_openmp' (and vice
versa?)?", or PR98012 "[OpenACC] 'gcc/fortran/scanner.c:include_line' should
consider 'flag_openacc' in addition to 'flag_openmp'?".