From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: Re: [Patch] OpenMP: Fix 'omp declare target' handling for vars [PR99509]
Date: Mon, 15 Mar 2021 09:20:50 +0100 [thread overview]
Message-ID: <20210315082050.GK231854@tucnak> (raw)
In-Reply-To: <93bf9c6b-1c60-017c-422c-5b4112f88509@codesourcery.com>
On Mon, Mar 15, 2021 at 09:17:47AM +0100, Tobias Burnus wrote:
> gcc/c/ChangeLog:
>
> PR c++/99509
> * c-decl.c (finish_decl): For 'omp declare target implicit' vars,
> ensure that the varpool node is marked as offloadable.
>
> gcc/cp/ChangeLog:
>
> PR c++/99509
> * decl.c (cp_finish_decl): For 'omp declare target implicit' vars,
> ensure that the varpool node is marked as offloadable.
>
> libgomp/ChangeLog:
>
> PR c++/99509
> * testsuite/libgomp.c-c++-common/declare_target-1.c: New test.
Ok, thanks.
Jakub
prev parent reply other threads:[~2021-03-15 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 14:20 Tobias Burnus
2021-03-12 12:20 ` Jakub Jelinek
2021-03-15 8:17 ` Tobias Burnus
2021-03-15 8:20 ` Jakub Jelinek [this message]
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=20210315082050.GK231854@tucnak \
--to=jakub@redhat.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tobias@codesourcery.com \
/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).