From: Tobias Burnus <tobias@codesourcery.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>
Subject: Pending OpenMP patches
Date: Fri, 24 Mar 2023 17:31:06 +0100 [thread overview]
Message-ID: <2f0595f5-1e46-22cb-d827-14a4a8f6a7e1@codesourcery.com> (raw)
Just to keep track myself, the following OpenMP are pending review - either
by Jakub or by me. It does not look as if any of those will get into GCC 13,
but who knows. I think the first three could:
[Doc patch - will go into GCC 13, still comments are welcome:]
[patch V2] Docs, OpenMP: Correct internal documentation of OMP_FOR
https://gcc.gnu.org/pipermail/gcc-patches/2023-March/614392.html
libgomp: Simplify OpenMP reverse offload host <-> device memory copy implementation
(was: [Patch] libgomp/nvptx: Prepare for reverse-offload callback handling)
https://gcc.gnu.org/pipermail/gcc-patches/2023-March/614569.html
[Patch,v4] Fortran/OpenMP: Fix mapping of array descriptors and deferred-length strings
https://gcc.gnu.org/pipermail/gcc-patches/2023-March/614472.html
[PATCH] openmp: Add support for 'present' modifier
https://gcc.gnu.org/pipermail/gcc-patches/2023-February/611299.html
[PATCH 0/3] OpenMP 5.0: Strided updates and array shape-operator support (C++)
https://gcc.gnu.org/pipermail/gcc-patches/2023-March/613785.html
[PATCH 0/7] openmp: OpenMP 5.1 loop transformation directives
https://gcc.gnu.org/pipermail/gcc-patches/2023-March/614564.html
[Patch] Fortran/OpenMP: Add parsing support for allocators/allocate directive
https://gcc.gnu.org/pipermail/gcc-patches/2022-December/608904.html
Complete patch set was just re-submitted by Julian, overview patch is
[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
- with follow up for 10/11 -
[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
Plus some more pending patches, some of which require re-diffing
or checking the backlog. Others are to be expected soon...
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
reply other threads:[~2023-03-24 16:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2f0595f5-1e46-22cb-d827-14a4a8f6a7e1@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).