From: Julian Brown <julian@codesourcery.com>
To: gcc-patches@gcc.gnu.org
Cc: fortran@gcc.gnu.org
Subject: Re: [PATCH v5 3/4] OpenMP: Pointers and member mappings
Date: Fri, 23 Dec 2022 14:53:30 +0000 [thread overview]
Message-ID: <20221223145330.3a41430b@squid.athome> (raw)
In-Reply-To: <20221215164650.332b5084@squid.athome>
On Thu, 15 Dec 2022 16:46:50 +0000
Julian Brown <julian@codesourcery.com> wrote:
> On Thu, 15 Dec 2022 14:54:58 +0000
> Julian Brown <julian@codesourcery.com> wrote:
>
> > On Wed, 7 Dec 2022 17:31:20 +0100
> > Tobias Burnus <tobias@codesourcery.com> wrote:
> >
> > > Hi Julian,
> > >
> > > I think this patch is OK; however, at least for gimplify.cc Jakub
> > > needs to have a second look.
> >
> > Thanks for the review! Here's a new version that hopefully
> > addresses your comments. (The gimplify bits change a bit more in
> > this version!)
>
> FYI, this is the current dependency list for this patch:
>
> (1) "OpenMP/OpenACC: Reindent TO/FROM/_CACHE_ stanza in
> {c_}finish_omp_clause"
> https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603791.html
> Approved.
>
> (2) "OpenMP/OpenACC: Rework clause expansion and nested struct
> handling"
> https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603792.html
> Approved, but waiting for *this* patch to avoid regressing Fortran
> pointer-mapping behaviour, and which Tobias noticed an issue with
> prior to committing, addressed by (4).
>
> (3) "OpenMP/OpenACC: Refine condition for when map clause expansion
> happens"
> https://gcc.gnu.org/pipermail/gcc-patches/2022-November/607543.html
> Not reviewed (partly OpenACC).
>
> (4) "OpenMP: implicitly map base pointer for array-section pointer
> components"
> https://gcc.gnu.org/pipermail/gcc-patches/2022-December/608318.html
> Not reviewed.
>
> The following patches also depend on this one and the above:
>
> (5) "OpenMP: lvalue parsing for map clauses (C++)"
> https://gcc.gnu.org/pipermail/gcc-patches/2022-November/605367.html
> Mostly approved.
>
> (6) "OpenMP: C++ "declare mapper" support"
> https://gcc.gnu.org/pipermail/gcc-patches/2022-November/607544.html
> Revised version unreviewed.
>
> ...and the to-be-revised "lvalue parsing for C", and C/Fortran
> "declare mapper" patches.
Followup:
https://gcc.gnu.org/pipermail/gcc-patches/2022-December/609031.html
next prev parent reply other threads:[~2022-12-23 14:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 10:39 [PATCH v5 0/4] OpenMP/OpenACC: Fortran array descriptor mappings Julian Brown
2022-10-18 10:39 ` [PATCH v5 1/4] OpenMP/OpenACC: Reindent TO/FROM/_CACHE_ stanza in {c_}finish_omp_clause Julian Brown
2022-10-18 10:39 ` [PATCH v5 2/4] OpenMP/OpenACC: Rework clause expansion and nested struct handling Julian Brown
2022-12-07 14:54 ` Tobias Burnus
2022-12-07 15:16 ` Julian Brown
2022-12-07 16:13 ` Tobias Burnus
2022-12-12 15:19 ` Julian Brown
2022-10-18 10:39 ` [PATCH v5 3/4] OpenMP: Pointers and member mappings Julian Brown
2022-12-07 16:31 ` Tobias Burnus
2022-12-15 14:54 ` Julian Brown
2022-12-15 16:46 ` Julian Brown
2022-12-23 14:53 ` Julian Brown [this message]
2022-10-18 10:39 ` [PATCH v5 4/4] OpenMP/OpenACC: Unordered/non-constant component offset runtime diagnostic Julian Brown
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=20221223145330.3a41430b@squid.athome \
--to=julian@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).