From: Jakub Jelinek <jakub@redhat.com>
To: Chung-Lin Tang <cltang@codesourcery.com>
Cc: Tobias Burnus <tobias@codesourcery.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Hafiz Abid Qadeer <abid_qadeer@mentor.com>,
Andrew Stubbs <ams@codesourcery.com>
Subject: Re: [PATCH, OpenMP, v2] Implement uses_allocators clause for target regions
Date: Mon, 6 Jun 2022 15:42:26 +0200 [thread overview]
Message-ID: <Yp4EQtaEfE4qPsTz@tucnak> (raw)
In-Reply-To: <79484359-fa27-ebe1-48f7-025e7fca0f49@codesourcery.com>
On Mon, Jun 06, 2022 at 09:38:30PM +0800, Chung-Lin Tang wrote:
> I'll file a bugzilla for the target construct.
Thanks.
> That said, can we delay FIELD_DECL support for uses_allocators? (which is target construct only)
> Since it appears to be not trivial at the moment.
Sure.
But would be nice to file a PR to track it once the patch is committed.
Jakub
next prev parent reply other threads:[~2022-06-06 13:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 13:20 [PATCH, OpenMP] " Chung-Lin Tang
2022-05-06 16:40 ` Tobias Burnus
2022-05-10 11:29 ` [PATCH, OpenMP, v2] " Chung-Lin Tang
2022-05-19 16:00 ` Jakub Jelinek
2022-05-19 17:02 ` Andrew Stubbs
2022-05-19 17:55 ` Jakub Jelinek
2022-05-20 6:59 ` Tobias Burnus
2022-05-19 17:46 ` Jakub Jelinek
2022-05-30 14:43 ` Chung-Lin Tang
2022-05-30 17:23 ` Jakub Jelinek
2022-05-31 10:02 ` Jakub Jelinek
2022-06-06 13:19 ` Chung-Lin Tang
2022-06-06 13:22 ` Jakub Jelinek
2022-06-06 13:38 ` Chung-Lin Tang
2022-06-06 13:42 ` Jakub Jelinek [this message]
2022-06-09 6:21 ` [PATCH, OpenMP, v4] " Chung-Lin Tang
2022-06-09 12:22 ` Jakub Jelinek
2022-06-13 13:29 ` Chung-Lin Tang
2022-06-13 14:04 ` Jakub Jelinek
2023-02-09 11:26 ` [og12] '{c-c++-common,gfortran.dg}/gomp/uses_allocators-*' -> 'libgomp.{c-c++-common,fortran}/uses_allocators-*' (was: [PATCH, OpenMP] Implement uses_allocators clause for target regions) Thomas Schwinge
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=Yp4EQtaEfE4qPsTz@tucnak \
--to=jakub@redhat.com \
--cc=abid_qadeer@mentor.com \
--cc=ams@codesourcery.com \
--cc=cltang@codesourcery.com \
--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).