public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/108382] [12/13 Regression] Incorrect parsing when acc and omp coexist and -fopenmp -fopenacc is used.
Date: Fri, 20 Jan 2023 17:08:30 +0000	[thread overview]
Message-ID: <bug-108382-4-tyIdB4OgEO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108382-4@http.gcc.gnu.org/bugzilla/>

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu.org
   Last reconfirmed|                            |2023-01-20
             Status|UNCONFIRMED                 |NEW
   Target Milestone|---                         |12.4
            Summary|Incorrect parsing when acc  |[12/13 Regression]
                   |and omp coexist and         |Incorrect parsing when acc
                   |-fopenmp -fopenacc is used. |and omp coexist and
                   |                            |-fopenmp -fopenacc is used.
     Ever confirmed|0                           |1

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
It seems as if for

  !$acc enter &
  !$acc   data
  !$omp flush &
  !$omp   RELEASE

a flag is wrong after parsing the second line; I think either the
'openacc_flag' needs to be (re)set to 0 or continue_flag needs to be set to 0.

(likewise for swapping omp and acc lines) 

Possibly be caused by the following commit as it works with GCC 11 but fails
with GCC 12:
  r12-1216-g4facf2bf5b7b32f444da864306b5c11e14c15bcf

  reply	other threads:[~2023-01-20 17:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 12:41 [Bug fortran/108382] New: " zbigniew.piotrowski at ecmwf dot int
2023-01-20 17:08 ` burnus at gcc dot gnu.org [this message]
2024-01-12 10:15 ` [Bug fortran/108382] [12/13/14 Regression] " rguenth at gcc dot gnu.org
2024-01-12 22:20 ` burnus at gcc dot gnu.org
2024-06-20  9:11 ` [Bug fortran/108382] [12/13/14/15 " rguenth 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-108382-4-tyIdB4OgEO@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).