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/105536] New: [OpenMP] Bogus "expected ‘concurrent’ before ‘reproducible’" Date: Mon, 09 May 2022 16:40:40 +0000 [thread overview] Message-ID: <bug-105536-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105536 Bug ID: 105536 Summary: [OpenMP] Bogus "expected ‘concurrent’ before ‘reproducible’" Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: diagnostic, openmp Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: jakub at gcc dot gnu.org Target Milestone: --- I think the message shown by C/C++ for the following is bogus: repro.c:3:23: error: expected ‘concurrent’ before ‘reproducible’ 3 | #pragma omp for order(reproducible) | ^~~~~~~~~~~~ The standard requires 'order(reproducible:concurrent)' – Thus, I expect *after* and not *before* in the error message. Cf. https://www.openmp.org/spec-html/5.1/openmpsu47.html#x72-720002.11.3 void f(void) { #pragma omp for order(reproducible) for (int i=0; i < 1; i++) ; } Side remark: Fortran is fine as it gives the following: 1 | !$omp do order(reproducible) | 1 Error: Expected ORDER(CONCURRENT) at (1) with optional ‘reproducible’ or ‘unconstrained’ modifier
next reply other threads:[~2022-05-09 16:40 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-09 16:40 burnus at gcc dot gnu.org [this message] 2022-05-09 16:49 ` [Bug c/105536] " 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-105536-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: 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).