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/101948] New: [OpenMP] gfc_split_omp_clauses + REDUCTION with TASK modifier Date: Tue, 17 Aug 2021 12:32:40 +0000 [thread overview] Message-ID: <bug-101948-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101948 Bug ID: 101948 Summary: [OpenMP] gfc_split_omp_clauses + REDUCTION with TASK modifier Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: openmp, rejects-valid Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: jakub at gcc dot gnu.org Target Milestone: --- I have not checked the spec – nor did I quickly spot in the C/C++ code where it is handled, however, there is a clause splitting differences between Fortran and C, which leads to an error. The C code compiles but Fortran gives: Error: invalid ‘task’ reduction modifier on construct other than ‘parallel’, ‘do’, ‘sections’ or ‘scope’ The Fortran code → (new file, commented; gfortran.dg/gomp/reduction-task-1.f90): !$omp teams distribute parallel do reduction (task, +: v) !$omp end teams distribute parallel do gives /* vvvvv - note task modifier. */ #pragma omp teams reduction(task,+:v) ... #pragma omp parallel reduction(task,+:v) While the C code (from c-c++-common/gomp/reduction-task-1.c): #pragma omp teams distribute parallel for reduction (task, +: v) gives #pragma omp teams reduction(+:v) #pragma omp parallel reduction(task,+:v)
next reply other threads:[~2021-08-17 12:32 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-17 12:32 burnus at gcc dot gnu.org [this message] 2021-08-17 12:42 ` [Bug fortran/101948] " jakub 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-101948-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).