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 middle-end/99928] [OpenMP] reduction variable in combined target construct wrongly mapped as firstprivate
Date: Thu, 13 May 2021 20:13:08 +0000 [thread overview]
Message-ID: <bug-99928-4-4UMbPEBP7v@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99928-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99928
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #7)
> Created attachment 50810 [details]
> Fortran version of the C testcases (see comment 7 for notes)
>
> Fortran conversion of the C/C++ testcases of comment 7 /
> r12-773-gd80aeff0bf2f455e9099def756f612bfbcd2cb0d
>
> Currently fails to compile due to those issues:
> * 'taskloop' not yet implemented
> * 'loop' not yet implemented
> * 'parallel master' not supported
> * 'reduction(+:r00[1:2])' not supported (also not with '[...]' replaced by
> '(...)')
I believe in Fortran those ought to be normal base language array sections,
so reduction(+:r00(2:3)) or so.
E.g. 5.0 says in [296:11] "The list items that appear in a reduction clause may
include array sections."
and [46:6-7] says: "Fortran has built-in support for array sections although
some restrictions apply to their use, as enumerated in the following section."
and later there are restrictions.
If we don't handle array sections in reduction, that would be missing item from
4.0 -> 4.5 support I think; do we handle array sections on map/to/from at
least?
next prev parent reply other threads:[~2021-05-13 20:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 8:39 [Bug middle-end/99928] New: " burnus at gcc dot gnu.org
2021-04-06 9:20 ` [Bug middle-end/99928] " jakub at gcc dot gnu.org
2021-04-10 17:23 ` burnus at gcc dot gnu.org
2021-05-06 15:59 ` jakub at gcc dot gnu.org
2021-05-06 16:23 ` burnus at gcc dot gnu.org
2021-05-06 16:35 ` jakub at gcc dot gnu.org
2021-05-13 15:16 ` cvs-commit at gcc dot gnu.org
2021-05-13 19:39 ` burnus at gcc dot gnu.org
2021-05-13 20:13 ` jakub at gcc dot gnu.org [this message]
2021-05-19 7:30 ` cvs-commit at gcc dot gnu.org
2021-05-20 7:20 ` cvs-commit at gcc dot gnu.org
2021-05-21 19:15 ` cvs-commit at gcc dot gnu.org
2021-05-21 19:20 ` cvs-commit at gcc dot gnu.org
2021-05-25 9:08 ` cvs-commit at gcc dot gnu.org
2021-05-28 9:34 ` cvs-commit at gcc dot gnu.org
2021-05-29 8:08 ` cvs-commit at gcc dot gnu.org
2021-06-01 10:48 ` cvs-commit at gcc dot gnu.org
2021-06-02 9:48 ` cvs-commit at gcc dot gnu.org
2021-06-04 10:08 ` cvs-commit at gcc dot gnu.org
2021-06-04 10:19 ` cvs-commit at gcc dot gnu.org
2021-06-04 12:04 ` burnus at gcc dot gnu.org
2021-06-08 7:52 ` cvs-commit at gcc dot gnu.org
2023-05-03 17:36 ` anlauf 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-99928-4-4UMbPEBP7v@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).