From: Tobias Burnus <tobias@codesourcery.com>
To: Julian Brown <julian@codesourcery.com>
Cc: <gcc-patches@gcc.gnu.org>, <fortran@gcc.gnu.org>, <jakub@redhat.com>
Subject: Re: [PATCH v7 3/5] OpenMP: Pointers and member mappings
Date: Mon, 11 Dec 2023 12:44:36 +0100 [thread overview]
Message-ID: <d8572c40-c0ca-46d3-8734-5238d9583323@codesourcery.com> (raw)
In-Reply-To: <20231207172449.2fb5765f@squid.athome>
Hi Julian,
On 07.12.23 18:24, Julian Brown wrote:
> On Wed, 6 Dec 2023 12:36:34 +0100
> Tobias Burnus<tobias@codesourcery.com> wrote:
>
>> LGTM, except for:
>>
>> * The 'target exit data' handling - comments below - looks a bit
>> fishy/inconsistent.
...
>> Thus, I wonder whether that shouldn't be instead
>> OMP_CLAUSE_MAP_KIND (node) == GOMP_MAP_DELETE
>> ? GOMP_MAP_DELETE : GOMP_MAP_RELEASE;
> I've fixed that as you suggest. Actually I've made OpenACC use the new
> node layout as well, since (a) it works and (b) it was weirdly
> inconsistent before. That is, exit data directives will no longer use
> e.g.:
>
> GOMP_MAP_FROM
> GOMP_MAP_TO_PSET
> GOMP_MAP_ATTACH_DETACH
>
> but instead,
>
> GOMP_MAP_FROM
> GOMP_MAP_RELEASE (with OMP_CLAUSE_RELEASE_DESCRIPTOR set)
> GOMP_MAP_ATTACH_DETACH
>
> actually the current state is that GOMP_MAP_TO_PSET will be used for
> the descriptor on an "exit data" directive if you refer to the whole
> array, but GOMP_MAP_RELEASE (etc.) will be used if you refer to an array
> section (without the flag newly added in this patch, of course). I
> don't think there's any reason to maintain that inconsistency.
...
> I've re-tested this version. Does it look better now?
Yes, LGTM as well.
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next prev parent reply other threads:[~2023-12-11 11:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 22:47 [PATCH v7 0/5] OpenMP/OpenACC: map clause and OMP gimplify rework Julian Brown
2023-08-18 22:47 ` [PATCH v7 1/5] OpenMP/OpenACC: Reindent TO/FROM/_CACHE_ stanza in {c_}finish_omp_clause Julian Brown
2023-08-18 22:47 ` [PATCH v7 2/5] OpenMP/OpenACC: Rework clause expansion and nested struct handling Julian Brown
2023-11-14 10:21 ` Tobias Burnus
2023-11-29 11:43 ` Julian Brown
2023-11-29 16:03 ` Tobias Burnus
2023-12-14 7:14 ` [committed] testsuite: Fix up target-enter-data-1.c on 32-bit targets Jakub Jelinek
2023-12-14 10:09 ` Julian Brown
2023-08-18 22:47 ` [PATCH v7 3/5] OpenMP: Pointers and member mappings Julian Brown
2023-12-06 11:36 ` Tobias Burnus
2023-12-07 17:24 ` Julian Brown
2023-12-11 11:44 ` Tobias Burnus [this message]
2023-08-18 22:47 ` [PATCH v7 4/5] OpenMP/OpenACC: Unordered/non-constant component offset runtime diagnostic Julian Brown
2023-12-14 14:26 ` Tobias Burnus
2023-12-15 13:00 ` Thomas Schwinge
2023-08-18 22:47 ` [PATCH v7 5/5] OpenMP/OpenACC: Reorganise OMP map clause handling in gimplify.cc Julian Brown
[not found] ` <20231216132507.5991c79e@squid.athome>
2023-12-19 15:41 ` Tobias Burnus
2023-12-20 21:29 ` Julian Brown
2023-12-21 8:51 ` Tobias Burnus
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=d8572c40-c0ca-46d3-8734-5238d9583323@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=julian@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).