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 c/99137] ICE in gimplify_scan_omp_clauses, at gimplify.c:9833 Date: Sat, 06 Mar 2021 10:51:52 +0000 [thread overview] Message-ID: <bug-99137-4-4jH5qmWy56@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99137-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99137 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #9 from Tobias Burnus <burnus at gcc dot gnu.org> --- FIXED on mainline (GCC 11), GCC 10 and GCC 9. Thanks for the report! As mentioned in the patch review at https://gcc.gnu.org/pipermail/gcc-patches/2021-March/566298.html the issue was discussed in a OpenACC spec meeting (Issue 354) and it was agreed but not yet voted on to use the OpenMP wording (valid assignment-expression). When writing that patch, I tried to find likewise issues with other clauses. Unless I missed one in 'gcc' or 'g++', it seems as if only 'async' was affected.
next prev parent reply other threads:[~2021-03-06 10:51 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-17 18:06 [Bug c/99137] New: " gscfq@t-online.de 2021-02-17 18:11 ` [Bug c/99137] " jakub at gcc dot gnu.org 2021-02-18 9:36 ` tschwinge at gcc dot gnu.org 2021-02-18 9:44 ` jakub at gcc dot gnu.org 2021-02-18 9:58 ` tschwinge at gcc dot gnu.org 2021-02-19 15:08 ` burnus at gcc dot gnu.org 2021-03-05 10:42 ` cvs-commit at gcc dot gnu.org 2021-03-06 10:21 ` cvs-commit at gcc dot gnu.org 2021-03-06 10:51 ` cvs-commit at gcc dot gnu.org 2021-03-06 10:51 ` burnus at gcc dot gnu.org [this message] 2021-07-01 9:36 ` tschwinge 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-99137-4-4jH5qmWy56@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).