public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>
Subject: OpenMP Patch Ping
Date: Thu, 24 Nov 2022 13:01:04 +0100	[thread overview]
Message-ID: <1e963b8f-a022-019b-513c-e0ad6cfa8b05@codesourcery.com> (raw)

Updated list as follow up to last ping at https://gcc.gnu.org/pipermail/gcc-patches/2022-September/601162.html


Recent patches:

Sandra's (Tue Nov 15 04:46:15 GMT 2022)
[PATCH v4] OpenMP: Generate SIMD clones for functions with "declare target"
https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606218.html


Julian's patches - I hope I got it right as I lost a bit track:

(Tue Nov 8 14:36:17 GMT 2022)
[PATCH v2 06/11] OpenMP: lvalue parsing for map clauses (C++)
https://gcc.gnu.org/pipermail/gcc-patches/2022-November/605367.html

(Fri Sep 30 13:30:22 GMT 2022)
[PATCH v3 06/11] OpenMP: Pointers and member mappings
https://gcc.gnu.org/pipermail/gcc-patches/2022-September/602609.html

(Tue Oct 18 10:39:01 GMT 2022)
[PATCH v5 0/4] OpenMP/OpenACC: Fortran array descriptor mappings
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/thread.html#603790
(I think this is partially my task to review those.)


Approved but waiting for the Fortran patches (v5) to get approved.
[PATCH v3 08/11] OpenMP/OpenACC: Rework clause expansion and nested struct handling
https://gcc.gnu.org/pipermail/gcc-patches/2022-September/602010.html


Possibly requiring a second look/review despite my initial comment
(which might require revisions on the patch side as well):
OpenMP: Duplicate checking for map clauses in Fortran (PR107214)
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/604033.html


Older patches:

* [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 ...)
* Re: [PATCH, OpenMP, Fortran] requires unified_shared_memory 2/2: insert USM allocators into libgfortran
   https://gcc.gnu.org/pipermail/gcc-patches/2022-September/601059.html

And finally:

* [PATCH, libgomp] Fix chunk_size<1 for dynamic schedule
   https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599332.html
(Side remark: some other debugging support like showing the mapping being done as stderr output or ... would be nice as well; might depend on a libgomp-debug.so and/or -f...(sanitize=openmp or ...); the other open-source compiler has something similar.)


  * * *


Pending libgomp/nvptx patches:

(Wed Sep 21 07:45:36 GMT 2022)
[PATCH, nvptx, 1/2] Reimplement libgomp barriers for nvptx
https://gcc.gnu.org/pipermail/gcc-patches/2022-September/601922.html

(Wed Sep 21 07:45:54 GMT 2022)
[PATCH, nvptx, 2/2] Reimplement libgomp barriers for nvptx: bar.red instruction support in GCC
https://gcc.gnu.org/pipermail/gcc-patches/2022-September/601925.html

Those were pinged 4 times :-(


Hopefully, I have not missed any patch

Tobias


PS: The following list covers pending patches, which have been reviewed but
but need to updated before being ready - hopefully, this list is also up to date:

* (No pending patch, but wwwdoc's changes-13.html + projects/gomp/ need an update before GCC 13)

* [Patch] OpenMP, libgomp, gimple: omp_get_max_teams, omp_set_num_teams, and
omp_{gs}et_teams_thread_limit on offload devices
Should be re-submitted any time soon (today, next few days)

* [Patch] OpenMP/Fortran: Permit end-clause on directive
   https://gcc.gnu.org/pipermail/gcc-patches/2022-August/600433.html
   Trivial patch modifications required - mostly LGTM already.

* [PATCH] libgomp: fix hang on fatal error
   https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603616.html
(Patch rejected but alternative solutions were suggested.)

* Re: [Patch] OpenMP/Fortran: Use firstprivat not alloc for ptr attach for arrays
(Committed but failing occasionally:)
https://gcc.gnu.org/pipermail/gcc-patches/2022-November/605854.html

* "[PATCH 3/3] vect: inbranch SIMD clones"
   https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599490.html
   Review comments to be addressed.

* [PATCH 0/5] [gfortran] Support for allocate directive (OpenMP 5.0)
   https://gcc.gnu.org/pipermail/gcc-patches/2022-January/588367.html

* [PATCH] openmp: fix max_vf setting for amdgcn offloading
   https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598265.html
→ To be updated for review comments.
(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, 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 split 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

             reply	other threads:[~2022-11-24 12:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 12:01 Tobias Burnus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-10 11:37 Tobias Burnus
2022-08-16 17:28 OpenMP patch ping Tobias Burnus
2022-09-06 15:01 ` Tobias Burnus
2020-11-27 16:09 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=1e963b8f-a022-019b-513c-e0ad6cfa8b05@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).