public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tburnus@baylibre.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>
Subject: [Patch] libgomp.texi: Update entries in OpenMP TR12 implementation status
Date: Thu, 4 Apr 2024 09:53:45 +0200	[thread overview]
Message-ID: <046f956d-a108-4b94-926a-7990075690d3@baylibre.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 913 bytes --]

Hi all,

this patch updates the OpenMP TR12 status (to-do) items:

(a) 'coexecute', added in TR12, was renamed after TR12 to
     'workdistribute'. Reason: Feedback that 'co...' reminds
     of Fortran coarrays and the its intrinsic procedures:
     co_broadcast, co_max, co_min, co_reduce, co_sum and
→ Honor this in the status but mention old name, hopefully,
   reducing some confusion and ensuring that we miss to update
   that entry once OpenMP 6.0 is released next November

(b) Since TR12, canonical loop nest forms can now be enclosed
     in { ... } in C/C++ or in BLOCK in Fortran. Add it to ensure
     we won't forget implementing this feature.

Comments, remarks, additions before I commit it?

Tobias

PS: There are surely more items I missed when updating the list
for TR12; I will either have a go later in this year or do it
when updating for the final OpenMP 6.0 in/after November this year.

[-- Attachment #2: tr12.diff --]
[-- Type: text/x-patch, Size: 1467 bytes --]

libgomp.texi: Update entries in OpenMP TR12 implementation status

libgomp/ChangeLog:

	* libgomp.texi (TR12): Honor post-TR12 directive name change; add
	item about curly braces/BLOCK permitted in canonical loop nests.

diff --git a/libgomp/libgomp.texi b/libgomp/libgomp.texi
index 1ae0f01ccdc..71d62105a20 100644
--- a/libgomp/libgomp.texi
+++ b/libgomp/libgomp.texi
@@ -515,7 +515,8 @@ Technical Report (TR) 12 is the second preview for OpenMP 6.0.
 @item @code{strict} modifier keyword to @code{num_threads} @tab N @tab
 @item @code{atomic} permitted in a construct with @code{order(concurrent)}
       @tab N @tab
-@item @code{coexecute} directive for Fortran @tab N @tab
+@item @code{workdistribute} directive for Fortran @tab N
+      @tab Renamed just after TR12; added in TR12 as @code{coexecute}
 @item Fortran DO CONCURRENT as associated loop in a @code{loop} construct
       @tab N @tab
 @item @code{threadset} clause in task-generating constructs @tab N @tab
@@ -539,6 +540,8 @@ Technical Report (TR) 12 is the second preview for OpenMP 6.0.
 
 @unnumberedsubsec Other new TR 12 features
 @multitable @columnfractions .60 .10 .25
+@item Canonical loop nest enclosed in (multiple) curly braces (C/C++) or BLOCK constructs (Fortran)
+      @tab N @tab
 @item Relaxed Fortran restrictions to the @code{aligned} clause @tab N @tab
 @item Mapping lambda captures @tab N @tab
 @item New @code{omp_pause_stop_tool} constant for omp_pause_resource @tab N @tab

                 reply	other threads:[~2024-04-04  7:53 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=046f956d-a108-4b94-926a-7990075690d3@baylibre.com \
    --to=tburnus@baylibre.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).