public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/100059] [OpenMP] wrong code with 'declare target link' and a scalar variable
Date: Mon, 04 Sep 2023 09:37:56 +0000 [thread overview]
Message-ID: <bug-100059-4-jhJ9fZ4wMw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100059-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100059
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tschwinge at gcc dot gnu.org
See Also| |https://github.com/MentorEm
| |bedded/nvptx-tools/pull/29
--- Comment #6 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #4)
> https://github.com/MentorEmbedded/nvptx-tools/pull/29
This is now finally incorporated, sorry for the (long...) delay.
Are you going to push the GCC-level test case (submitted in this PR), or want
me to? For nvptx offloading, it'll FAIL its execution test until nvptx-tools
updated, but that's OK in my opinion.
next prev parent reply other threads:[~2023-09-04 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 8:58 [Bug middle-end/100059] New: " burnus at gcc dot gnu.org
2021-04-13 13:16 ` [Bug middle-end/100059] " burnus at gcc dot gnu.org
2021-04-13 13:37 ` burnus at gcc dot gnu.org
2021-04-13 14:11 ` burnus at gcc dot gnu.org
2021-04-13 16:39 ` burnus at gcc dot gnu.org
2022-03-29 10:23 ` burnus at gcc dot gnu.org
2023-09-04 9:37 ` tschwinge at gcc dot gnu.org [this message]
2023-09-04 12:57 ` [Bug other/100059] " tschwinge 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-100059-4-jhJ9fZ4wMw@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).