public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/98014] [Fortran OpenACC] Empty '!$acc' continuation line rejected Date: Mon, 15 Feb 2021 10:25:38 +0000 [thread overview] Message-ID: <bug-98014-4-HDRrrH4bGF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98014-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98014 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- !$omp parallel & !$omp num_threads(4) & !$omp !comment !$omp end parallel end is also rejected. And in !$omp parallel & !$omp num_threads(4) & !$omp&!comment !$omp end parallel end we treat that !$omp& as the last continuation line and accept it, but as the & is the last non-blank character before comment, shouldn't that mean a continuation is required?
next prev parent reply other threads:[~2021-02-15 10:25 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-26 11:20 [Bug fortran/98014] New: " tschwinge at gcc dot gnu.org 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 [this message] 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-HDRrrH4bGF@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: linkBe 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).