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>
Cc: Jakub Jelinek <jakub@redhat.com>
Subject: [wwwdocs] projects/gomp/: Update TR12 status - fix misplaced GCC-14; add new items
Date: Thu, 4 Apr 2024 10:01:36 +0200	[thread overview]
Message-ID: <27bb1379-16dd-4506-a107-dd976b37f4b1@baylibre.com> (raw)


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

TR12 update:
* I misplaced one implemented in GCC 14 in one of the last commits
* Same update as just proposed for libgomp.texi:
   - Renaming of 'coexecute' to 'workdistribute'
     (Post TR12 change to avoid confusion with Fortran's co_min,
      co_broadcast, ... intrinsic procedures for coarrays)
   - Add item about { } / BLOCK in canonical loop nests

Comments, suggestions, other remarks before I commit it?

Current version:file:///home/tob/repos/gcc-wwwdocs/htdocs/projects/gomp/index.html

Tobias

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

projects/gomp/: Update TR12 status - fix misplaced GCC-14; add new items

diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html
index b8f11508..798efb21 100644
--- a/htdocs/projects/gomp/index.html
+++ b/htdocs/projects/gomp/index.html
@@ -846,7 +846,7 @@ than listed, depending on resolved corner cases and optimizations.</p>
   </tr>
   <tr>
     <td><code>declare mapper</code> with iterator and <code>present</code> modifiers</td>
-    <td class="supported"><a href="../../gcc-14/changes.html#languages">GCC&nbsp;14</a></td>
+    <td class="unsupported">No</td>
     <td></td>
   </tr>
   <tr>
@@ -871,7 +871,7 @@ than listed, depending on resolved corner cases and optimizations.</p>
   </tr>
   <tr>
     <td>New <code>allocators</code> directive for Fortran</td>
-    <td class="unsupported">No</td>
+    <td class="supported"><a href="../../gcc-14/changes.html#languages">GCC&nbsp;14</a></td>
     <td></td>
   </tr>
   <tr>
@@ -1225,9 +1225,9 @@ error.</p>
     <td></td>
   </tr>
   <tr>
-    <td><code>coexecute</code> directive for Fortran</td>
+    <td><code>workdistribute</code> directive for Fortran</td>
     <td class="unsupported">No</td>
-    <td></td>
+    <td>Renamed just after TR12; added in TR12 as <code>coexecute</code></td>
   </tr>
   <tr>
     <td>Fortran DO CONCURRENT as associated loop in a <code>loop</code>
@@ -1295,6 +1295,11 @@ error.</p>
     <td class="unsupported">No</td>
     <td></td>
   </tr>
+  <tr>
+    <td>Canonical loop nest enclosed in (multiple) curly braces (C/C++) or BLOCK constructs (Fortran)</td>
+    <td class="unsupported">No</td>
+    <td></td>
+  </tr>
   <tr>
     <td>Relaxed Fortran restrictions to the <code>aligned</code> clause</td>
     <td class="unsupported">No</td>

                 reply	other threads:[~2024-04-04  8:01 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=27bb1379-16dd-4506-a107-dd976b37f4b1@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).