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/93826] [OpenMP][OpenACC] Collapsed loop – code silently ignored
Date: Fri, 22 May 2020 08:37:30 +0000 [thread overview]
Message-ID: <bug-93826-4-1eGQJCYmO5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93826-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93826
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> ---
OpenMP 5 lists under changes:
"The collapse of associated loops that are imperfectly nested loops was defined
for the worksharing-loop (see Section 2.9.2 on page 10), simd (see Section
2.9.3.1 on page 110), taskloop (see Section 2.10.2 on page 140) and distribute
(see Section 2.9.4.2 on page 123) constructs."
worksharing: https://www.openmp.org/spec-html/5.0/openmpsu41.html
simd: https://www.openmp.org/spec-html/5.0/openmpsu42.html
taskloop: https://www.openmp.org/spec-html/5.0/openmpsu47.html
distribute: https://www.openmp.org/spec-html/5.0/openmpsu43.html
Both C and Fortran example compile with PGI, PGI does set the variable to
"x=5".
The Intel compiler rejects C + Fortran code, Clang rejects the C example.
Hence:
– OpenMP 4.5:
* gfortran has accept-invalid+diagnostic bug
- OpenMP 5:
* gfortran needs to diagnose 'order(concurrent)'
(once the 'order' clause is implemented)
* gcc/g++/gfortran needs to handle intervening code in the other cases.
- OpenACC: need to reject the code.
next prev parent reply other threads:[~2020-05-22 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-93826-4@http.gcc.gnu.org/bugzilla/>
2020-05-22 8:03 ` burnus at gcc dot gnu.org
2020-05-22 8:14 ` burnus at gcc dot gnu.org
2020-05-22 8:37 ` burnus at gcc dot gnu.org [this message]
2020-08-06 9:32 ` burnus at gcc dot gnu.org
2020-08-06 12:53 ` dominiq at lps dot ens.fr
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-93826-4-1eGQJCYmO5@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).