From: Tobias Burnus <tobias@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: OpenMP Patch Ping – including "[13 Regression]" patches
Date: Tue, 14 Feb 2023 10:40:54 +0100 [thread overview]
Message-ID: <6a71c5c6-8b03-ad90-f30b-a5df20a71758@codesourcery.com> (raw)
In-Reply-To: <a2f19c62-8e29-1008-f013-fc795fd35abe@codesourcery.com>
* The 'loop' patch fixes a long-standing bug exposed by a GCC 13 commit,
making it a "13 Regression" fix
* The next two are simple bug fixes, relatively obvious and have very
limited-scope code changes - fixing wrong-code issues.
* The next two are a bit longer but also rather contained.
* Julian's patch set fixes several real bugs (such as PR108624), but it unfortunately
more complex; still, it would be good if they could be eventually be reviewed ...
[Patch][v2] OpenMP/Fortran: Fix loop-iter var privatization with !$OMP LOOP [PR108512]
https://gcc.gnu.org/pipermail/gcc-patches/2023-February/611730.html
[Patch] libgomp: Fix 'target enter data' with always pointer
https://gcc.gnu.org/pipermail/gcc-patches/2023-February/611920.html
[Patch] libgomp: Fix reverse-offload for GOMP_MAP_TO_PSET
https://gcc.gnu.org/pipermail/gcc-patches/2023-February/611429.html
[PATCH] openmp: Add support for 'present' modifier"
https://gcc.gnu.org/pipermail/gcc-patches/2023-February/611299.html
[Patch] Fortran/OpenMP: Add parsing support for allocators/allocate directive
https://gcc.gnu.org/pipermail/gcc-patches/2022-December/608904.html
[PATCH v6 00/11] OpenMP: C/C++ lvalue parsing, C/C++/Fortran "declare mapper" support
https://gcc.gnu.org/pipermail/gcc-patches/2022-December/thread.html#609031
Note: For 10/11 of the set, there was a follow up:
[PATCH v6 10/11] OpenMP: Support OpenMP 5.0 "declare mapper" directives for C
https://gcc.gnu.org/pipermail/gcc-patches/2023-January/609566.html
On 07.02.23 17:34, Tobias Burnus wrote:
> On 10.01.23 12:37, Tobias Burnus wrote [with FYI comments omitted]:
> ...
>> Fortran deep mapping (allocatable components)
>>
>> [Patch][1/2] OpenMP: Add lang hooks + run-time filled map arrays for
>> Fortran deep mapping of DT
>> https://gcc.gnu.org/pipermail/gcc-patches/2023-January/609637.html
>
> PS: NOTE to the list above: I have stopped checking older patches. I know
> some more are pending review, others need to be revised. I will re-check,
> once the below listed patches have been reviewed. Cf. old list.
Thanks,
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
prev parent reply other threads:[~2023-02-14 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 11:37 OpenMP Patch Ping Tobias Burnus
2023-01-28 17:36 ` OpenMP Patch Ping – including "[13 Regression]" patches Tobias Burnus
2023-02-07 16:34 ` Tobias Burnus
2023-02-14 9:40 ` Tobias Burnus [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=6a71c5c6-8b03-ad90-f30b-a5df20a71758@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).