public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/98014] New: [Fortran OpenACC] Empty '!$acc' continuation line rejected
Date: Thu, 26 Nov 2020 11:20:10 +0000 [thread overview]
Message-ID: <bug-98014-4@http.gcc.gnu.org/bugzilla/> (raw)
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'?".
next reply other threads:[~2020-11-26 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 11:20 tschwinge at gcc dot gnu.org [this message]
2021-02-14 18:02 ` [Bug fortran/98014] " dominiq at lps dot ens.fr
2021-02-15 10:25 ` jakub at gcc dot gnu.org
2021-02-15 12:08 ` [Bug fortran/98014] [Fortran][OpenACC][OpenMP] Empty '!$acc'/'!$omp' " burnus at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-98014-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).