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 c/99137] ICE in gimplify_scan_omp_clauses, at gimplify.c:9833
Date: Thu, 18 Feb 2021 09:44:45 +0000	[thread overview]
Message-ID: <bug-99137-4-pCnbOGx2IS@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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
ice-on-invalid-code is when an error should be reported and instead of that the
compiler crashes.
ice-on-valid-code is when the code should compile without errors (perhaps with
warnings, and not considering warnings promoted to errors) but the compiler
crashes on it instead.
I have no idea what OpenACC says about this if anything, in OpenMP we've
clarified that in clauses all the expressions in the grammar except a few
explicitly mentioned cases are assignment expressions and so commas should
appear there only nested, like schedule(static, (1, 2)) is valid, while
schedule(static, 1, 2) is invalid.
"Each of the expressions used in the OpenMP syntax inside of the clauses must
be a valid assignment-expression of the base language unless otherwise
specified."

  parent reply	other threads:[~2021-02-18  9:44 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 [this message]
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
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-pCnbOGx2IS@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).