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 middle-end/103416] [OpenMP] Double mapping via firstprivate(n) map(to:n [len: 4][implicit])
Date: Thu, 02 Dec 2021 11:07:46 +0000 [thread overview]
Message-ID: <bug-103416-4-Dx0kxfpujI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103416-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103416
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[12 Regression][OpenMP] |[OpenMP] Double mapping via
|Bogus firstprivate(n) |firstprivate(n) map(to:n
|map(to:n [len: |[len: 4][implicit])
|4][implicit]) |
Keywords|wrong-code |missed-optimization
--- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> ---
I changed the bug subject as the "12 Regression" issue has been fixed (cf.
below,
committed with reference to PR90030 not to this PR) – but the code-improvement
part still remains to be done.
* * *
(In reply to Chung-Lin Tang from comment #1)
> Can you see if adding this patch:
> https://gcc.gnu.org/pipermail/gcc-patches/2021-November/583279.html
> fixes this problem? If so, then it should be another occurrence of PR90030
This patch is now committed:
commit r12-5706-g1ac7a8c9e4798d352eb8c64905dd38086af4e1cd
Author: Chung-Lin Tang <cltang@codesourcery.com>
Date: Thu Dec 2 18:24:03 2021 +0800
fortran: OpenMP/OpenACC array mapping alignment fix (PR90030)
* * *
TODO: LOOP VAR double mapping – cf. PR80330, i.e.
map(to:D.4217 [len: 4][implicit]) map(tofrom:n [len: 4][implicit])
where the loop variable is mapped twice.
See Comment 4 for what remains to be done and a draft patch.
next prev parent reply other threads:[~2021-12-02 11:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 18:41 [Bug middle-end/103416] New: [12 Regression][OpenMP] Bogus " burnus at gcc dot gnu.org
2021-11-24 19:05 ` [Bug middle-end/103416] " cltang at gcc dot gnu.org
2021-11-25 7:18 ` rguenth at gcc dot gnu.org
2021-11-25 10:07 ` burnus at gcc dot gnu.org
2021-11-25 10:52 ` burnus at gcc dot gnu.org
2021-11-25 11:21 ` burnus at gcc dot gnu.org
2021-11-25 11:24 ` burnus at gcc dot gnu.org
2021-12-02 11:07 ` burnus at gcc dot gnu.org [this message]
2022-05-06 8:32 ` [Bug fortran/103416] [OpenMP] Double mapping via firstprivate(n) map(to:n [len: 4][implicit]) of loop bounds jakub at gcc dot gnu.org
2023-05-08 12:23 ` rguenth 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-103416-4-Dx0kxfpujI@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).