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. dc54aeee47a0a7cd24220c27788e2ce3ddd6e4c5
Date: Fri, 24 Nov 2023 16:40:03 +0000 (GMT)	[thread overview]
Message-ID: <20231124164003.2D541385840E@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  dc54aeee47a0a7cd24220c27788e2ce3ddd6e4c5 (commit)
      from  17418f262b17680a07a4493631aa0743b5fe9780 (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 dc54aeee47a0a7cd24220c27788e2ce3ddd6e4c5
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Fri Nov 24 17:39:29 2023 +0100

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

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 455798d1..4eac9d6e 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -53,10 +53,16 @@ a work-in-progress.</p>
       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.0: The <code>allocate/<code> directive is now
+      supported for stack variables in C and Fortran, including the OpenMP 5.1
+      <code>align</code> modifier.
     <li>
       OpenMP 5.1: Support was added for collapsing imperfectly nested loops and
       using <code>present</code> as map-type modifier and in
-      <code>defaultmap</code>.
+      <code>defaultmap</code>. The <code>indirect</code> clause is now supported
+      for C and C++.  The performance of copying strided data from or to nvptx
+      devices using the OpenMP 5.1 routine <code>omp_target_memcpy_rect</code>
+      has been improved.
     </li>
     <li>
       OpenMP 5.2: The <code>OMP_TARGET_OFFLOAD=mandatory</code> handling has
@@ -64,10 +70,13 @@ a work-in-progress.</p>
       For Fortran, the list of directives permitted in Fortran pure procedures
       was extended. Additionally, the spec change has been implemented for
       default implicit mapping of C/C++ pointers pointing to unmapped storage.
+      The <code>destroy</code> now optionally accepts the depend object as
+      argument.
     </li>
     <li>
-      OpenMP 6.0 preview (TR11): The <code>decl</code> attribute is now
-      supported in C++ 11 attributes.
+      OpenMP 6.0 preview (TR11/TR12): The <code>decl</code> attribute is now
+      supported in C++ 11 and the <code>directive</code>, <code>sequence</code>
+      and <code>decl</code> attributes are now supported in C 23.
     </li>
     <li>
       The <a href="https://gcc.gnu.org/onlinedocs/libgomp/">GNU Offloading and
diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html
index bc472747..03f74a88 100644
--- a/htdocs/projects/gomp/index.html
+++ b/htdocs/projects/gomp/index.html
@@ -821,7 +821,7 @@ than listed, depending on resolved corner cases and optimizations.</p>
   </tr>
   <tr>
     <td>Deprecation of no-argument <code>destroy</code> clause on <code>depobj</code></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>

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

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


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-11-24 16:40 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=20231124164003.2D541385840E@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).