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>,
	Gerald Pfeifer <gerald@pfeifer.com>
Subject: [wwwdocs] gcc-14/changes.html + projects/gomp/: GCC 14 OpenMP update
Date: Tue, 13 Jun 2023 20:45:33 +0200	[thread overview]
Message-ID: <bbc0e7c7-27e0-c6e1-7fa0-c2283ee2903b@codesourcery.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 681 bytes --]

First update for OpenMP changes that made it into GCC 14.

Wording, technical and other comments are welcome as always.

I intent to commit the attached patch tomorrow.

Tobias

PS: There were a bunch of other useful changes, but those "only" improved
and fixed features already supported or added parsing-only support. Thus,
while the former is important for users, it is not for the release notes.
-----------------
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

[-- Attachment #2: gcc-14-omp.diff --]
[-- Type: text/x-patch, Size: 3399 bytes --]

gcc-14/changes.html + projects/gomp/: GCC 14 OpenMP update

 htdocs/gcc-14/changes.html      | 15 +++++++++++++++
 htdocs/projects/gomp/index.html | 10 ++++++----
 2 files changed, 21 insertions(+), 4 deletions(-)

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 55d566b8..c403c94f 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -37,6 +37,21 @@ a work-in-progress.</p>
 <!-- .................................................................. -->
 <h2 id="general">General Improvements</h2>
 
+<ul>
+  <li id="openmp"><a href="https://gcc.gnu.org/projects/gomp/">OpenMP</a>
+  <ul>
+    <li>
+      The <code>requires</code> directive's <code>unified_address</code>
+      requirement is now fulfilled by both AMD GCN and nvptx devices.
+    </li>
+    <li>
+      OpenMP 5.2: The <code>OMP_TARGET_OFFLOAD=mandatory</code> handling has
+      been updated for the clarifications and changes of the 5.2 specification.
+      For Fortran, the list of directives permitted in Fortran pure procedures
+      was extended.
+    </li>
+  </ul>
+</ul>
 <!-- .................................................................. -->
 <h2 id="languages">New Languages and Language specific improvements</h2>
 
diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html
index 328d17bd..55066f68 100644
--- a/htdocs/projects/gomp/index.html
+++ b/htdocs/projects/gomp/index.html
@@ -142,7 +142,7 @@ filing a <a href="../../bugs/">bug report</a>.</p>
 
 <p>Implementation status in libgomp manual:
 <a href="https://gcc.gnu.org/onlinedocs/libgomp/OpenMP-Implementation-Status.html"
->Mainline (GCC 13)</a>,
+>Mainline (GCC 14)</a>,
 <a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/libgomp/OpenMP-Implementation-Status.html"
 >GCC 13</a>,
 <a href="https://gcc.gnu.org/onlinedocs/gcc-12.1.0/libgomp/OpenMP-Implementation-Status.html"
@@ -313,12 +313,14 @@ than listed, depending on resolved corner cases and optimizations.</p>
       <a href="../../gcc-9/changes.html#c-family">GCC&nbsp;9</a><br>
       <a href="../../gcc-12/changes.html#languages">GCC&nbsp;12</a><br>
       <a href="../../gcc-13/changes.html#languages">GCC&nbsp;13</a>
+      <a href="../../gcc-14/changes.html#languages">GCC&nbsp;14</a>
     </td>
     <td>
       (<code>atomic_default_mem_order</code>)<br>
       (<code>dynamic_allocators</code>)<br>
       complete but no non-host devices provides <code>unified_address</code> or
-      <code>unified_shared_memory</code>
+      <code>unified_shared_memory</code><br>
+      complete but no non-host devices provides <code>unified_shared_memory</code>
     </td>
   </tr>
   <tr>
@@ -836,7 +838,7 @@ than listed, depending on resolved corner cases and optimizations.</p>
   </tr>
   <tr>
     <td>Extended list of directives permitted in Fortran pure procedures</td>
-    <td class="unsupported">No</td>
+    <td class="supported"><a href="../../gcc-13/changes.html#languages">GCC&nbsp;14</a></td>
     <td></td>
   </tr>
   <tr>
@@ -926,7 +928,7 @@ than listed, depending on resolved corner cases and optimizations.</p>
   </tr>
   <tr>
     <td>Initial value of <em>default-device-var</em> ICV with <code>OMP_TARGET_OFFLOAD=mandatory</code></td>
-    <td class="unsupported">No</td>
+    <td class="supported"><a href="../../gcc-13/changes.html#languages">GCC&nbsp;14</a></td>
     <td></td>
   </tr>
   <tr>

             reply	other threads:[~2023-06-13 18:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13 18:45 Tobias Burnus [this message]
2023-06-14  8:10 ` 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=bbc0e7c7-27e0-c6e1-7fa0-c2283ee2903b@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.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).