From: Tobias Burnus <tobias@codesourcery.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>
Subject: OpenMP patch ping
Date: Tue, 16 Aug 2022 19:28:24 +0200 [thread overview]
Message-ID: <c4bd5262-2261-3603-78c7-bfc9d1b731a1@codesourcery.com> (raw)
I would like to ping the following OpenMP patches.
First two non-pings but just RFC:
- "Restore 'GOMP_offload_unregister_ver' functionality"
https://gcc.gnu.org/pipermail/gcc-patches/2022-July/597918.html
* QUESTION: See 'assert' question in email exchange
(linked email message + emails before/after it in the thread)
- [Patch] OpenMP: Fix folding with simd's linear clause [PR106492]
https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599308.html
* Already committed as obvious to mainline + GCC 12
* Question: Close PR or also backport to GCC 11? Other patch comments?
Now the patch pings – lightly ordered by complexity:
* [PATCH, OpenMP, C++] Allow classes with static members to be mappable
https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598918.html
* Modified as requested in the patch review
* [Patch] OpenMP: Fix var replacement with 'simd' and linear-step vars [PR106548]
https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599832.html
* [Patch] Fortran: OpenMP fix declare simd inside modules and absent linear step [PR106566]
https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599829.html
* [patch] libgomp/splay-tree.h: Fix splay_tree_prefix handling
https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598694.html
* [Patch] OpenMP requires: Fix diagnostic filename corner case
https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598697.html
* [PATCH] openmp: fix max_vf setting for amdgcn offloading
https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598265.html
(Side note: we should at some point find a way to improve target-specific
handling; similar to the are-exceptions-supported issue of PR101544 but
there are more.)
* [PATCH] OpenMP, libgomp: Environment variable syntax extension.
https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598770.html
* Post-review Revised patch
* [Patch] OpenMP, libgomp, gimple: omp_get_max_teams, omp_set_num_teams, and omp_{gs}et_teams_thread_limit on offload devices
https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599278.html
* Revised patch; saw a light review before
* [Patch] OpenMP: Support reverse offload (middle end part)
https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598662.html
(Does permanent host fallback for target regions; I have a WIP patch
for AMDGCN and nvptx)
* [PATCH 0/3] OpenMP SIMD routines
https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599487.html
* [PATCH 0/5] [gfortran] Support for allocate directive (OpenMP 5.0)
https://gcc.gnu.org/pipermail/gcc-patches/2022-January/588367.html
(already older - but I missed to ping it.)
* [PATCH 00/17] openmp, nvptx, amdgcn: 5.0 Memory Allocators
https://gcc.gnu.org/pipermail/gcc-patches/2022-July/597976.html
* Unified-Shared Memory & Pinned Memory
Depending on those:
* [PATCH] OpenMP, libgomp: Handle unified shared memory in omp_target_is_accessible.
https://gcc.gnu.org/pipermail/gcc-patches/2022-May/594187.html
* [PATCH, OpenMP, Fortran] requires unified_shared_memory 1/2: adjust libgfortran memory allocators
https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599703.html
(Fortran part, required for ...)
* [PATCH, OpenMP, Fortran] requires unified_shared_memory 2/2: insert USM allocators into libgfortran
https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599704.html
And finally:
* [PATCH, libgomp] Fix chunk_size<1 for dynamic schedule
https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599332.html
Tobias
PS: I hope the list above and the one below is somewhat complete...
* * *
PPS: Tracking patches pending (re)submissions, just that it is not
forgotten on our side:
* [PATCH, OpenMP, v4] Implement uses_allocators clause for target regions
https://gcc.gnu.org/pipermail/gcc-patches/2022-June/596587.html
* Needs to be revised according to review comments
* Fortran allocatable components handling (needs to be slit into separate pieces and submitted
separately)
https://gcc.gnu.org/pipermail/gcc-patches/2022-April/593704.html
* [PATCH 00/16] OpenMP: lvalues in "map" clauses and struct handling rework
https://gcc.gnu.org/pipermail/gcc-patches/2021-December/586600.html
and January + February updates (search for metadirective)
+ patch review end of May, e.g.
https://gcc.gnu.org/pipermail/gcc-patches/2022-May/595762.html (+ 4 more emails)
* [PATCH 00/16] OpenMP: lvalues in "map" clauses and struct handling rework
https://gcc.gnu.org/pipermail/gcc-patches/2021-November/585439.html
+ [PATCH v2 00/11] OpenMP 5.0: C & C++ "declare mapper" support (plus struct rework, etc.)
https://gcc.gnu.org/pipermail/gcc-patches/2022-March/591973.html
* [PATCH 00/40] OpenACC "kernels" Improvements
https://gcc.gnu.org/pipermail/gcc-patches/2021-December/586901.html
(4 simple patches are in by now; could be reviewed, in principle)
-----------------
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 reply other threads:[~2022-08-16 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 17:28 Tobias Burnus [this message]
2022-09-06 15:01 ` Tobias Burnus
-- strict thread matches above, loose matches on Subject: below --
2023-01-10 11:37 OpenMP Patch Ping Tobias Burnus
2022-11-24 12:01 Tobias Burnus
2020-11-27 16:09 OpenMP patch ping 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=c4bd5262-2261-3603-78c7-bfc9d1b731a1@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).