public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Tobias Burnus <burnus@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. b286a7932a63eb192e5586f7534ed508fca0c7f0
Date: Wed, 14 Jun 2023 08:05:00 +0000 (GMT)	[thread overview]
Message-ID: <20230614080500.0B02E3858D38@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  b286a7932a63eb192e5586f7534ed508fca0c7f0 (commit)
      from  9203cc1348752fcf7e414bceab65f9035d45203c (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit b286a7932a63eb192e5586f7534ed508fca0c7f0
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Wed Jun 14 10:03:16 2023 +0200

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

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..2df67403 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>
@@ -791,7 +793,7 @@ than listed, depending on resolved corner cases and optimizations.</p>
   </tr>
   <tr>
     <td>Clauses on <code>end</code> directive can be on directive</td>
-    <td class="unsupported">No</td>
+    <td class="supported"><a href="../../gcc-13/changes.html#languages">GCC&nbsp;13</a></td>
     <td></td>
   </tr>
   <tr>
@@ -801,7 +803,7 @@ than listed, depending on resolved corner cases and optimizations.</p>
   </tr>
   <tr>
     <td><code>linear</code> clause syntax changes and <code>step</code> modifier</td>
-    <td class="unsupported">No</td>
+    <td class="supported"><a href="../../gcc-13/changes.html#languages">GCC&nbsp;13</a></td>
     <td></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>

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-14/changes.html      | 15 +++++++++++++++
 htdocs/projects/gomp/index.html | 14 ++++++++------
 2 files changed, 23 insertions(+), 6 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-06-14  8:05 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=20230614080500.0B02E3858D38@sourceware.org \
    --to=burnus@sourceware.org \
    --cc=gcc-cvs-wwwdocs@gcc.gnu.org \
    /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).