public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/109701] I have a MWE where an omp reduction breaks if I add the option for GPU offloading (even if it isn't used).
Date: Tue, 02 May 2023 19:35:49 +0000 [thread overview]
Message-ID: <bug-109701-4-u9MlQBhKMq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109701-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109701
--- Comment #3 from anlauf at gcc dot gnu.org ---
(In reply to Thomas Meltzer from comment #1)
> Could be related to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99928 but I
> am not sure. In my case the GPU offloading should be ignored.
Replacing the line
!$omp target teams if(is_GPU) !<---- comment this
by
!$omp target teams if(is_GPU) map(max_diff)
seems to make a difference for me. So it might be related to pr99928.
next prev parent reply other threads:[~2023-05-02 19:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 17:07 [Bug fortran/109701] New: " thomas.meltzer1 at gmail dot com
2023-05-02 17:10 ` [Bug fortran/109701] " thomas.meltzer1 at gmail dot com
2023-05-02 19:05 ` anlauf at gcc dot gnu.org
2023-05-02 19:35 ` anlauf at gcc dot gnu.org [this message]
2023-05-03 8:30 ` thomas.meltzer1 at gmail dot com
2023-05-03 17:45 ` jakub at gcc dot gnu.org
2023-05-04 16:08 ` thomas.meltzer1 at gmail dot com
2023-05-04 16:41 ` 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-109701-4-u9MlQBhKMq@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).