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. 31e3c804b41bf457546e0d16332379192fc57218
Date: Wed, 10 Jan 2024 08:12:33 +0000 (GMT)	[thread overview]
Message-ID: <20240110081233.58DBB3858426@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  31e3c804b41bf457546e0d16332379192fc57218 (commit)
      from  5ab74dd64c5892b42d0ac0cb9a468882df224845 (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 31e3c804b41bf457546e0d16332379192fc57218
Author: Tobias Burnus <burnus@net-b.de>
Date:   Wed Jan 10 09:12:03 2024 +0100

    gcc-14/changes.html: OpenMP - improve wording
    
    This is mostly some shifting of items in bullet points to make it
    more organized; it also improved the wording a bit. And there is one
    new feature: the optimization for omp_target_memcpy_rect is now also
    done for AMD GPUs and not only for nvptx.

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index e3a68998..2c64cf67 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -49,14 +49,24 @@ a work-in-progress.</p>
 <ul>
   <li id="openmp"><a href="https://gcc.gnu.org/projects/gomp/">OpenMP</a>
   <ul>
+    <li>
+      The <a href="https://gcc.gnu.org/onlinedocs/libgomp/">GNU Offloading and
+      Multi Processing Runtime Library Manual</a> has been updated and extended,
+      improving especially the description of <abbr title="internal control
+      variables">ICVs</abbr>, memory allocation, environment variables and OpenMP
+      routines.
+    </li>
     <li>
       The <code>requires</code> directive's <code>unified_address</code>
       requirement is now fulfilled by both AMD GCN and nvptx devices.
       AMD GCN and nvptx devices now support low-latency allocators as
       <a href="https://gcc.gnu.org/onlinedocs/libgomp/Offload-Target-Specifics.html"
       >detailed in the manual</a>. Initial support for pinned-memory
-      allocators has been added (<a href="https://gcc.gnu.org/onlinedocs/libgomp/Memory-allocation.html"
-      >as detailed in the manual</a>)
+      allocators has been added and, on Linux,
+      <a href="https://github.com/numactl/numactl">libnuma</a> is now used
+      for allocators requesting the nearest-partition trait (both is described
+      in the <a href="https://gcc.gnu.org/onlinedocs/libgomp/Memory-allocation.html"
+      >memory allocation section of the manual</a>).
     </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
@@ -74,8 +84,8 @@ a work-in-progress.</p>
       using <code>present</code> as map-type modifier and in
       <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.
+      and AMD GPU 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
@@ -83,23 +93,14 @@ 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.
+      The <code>destroy</code> clause now optionally accepts the depend object
+      as argument.
     </li>
     <li>
       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
-      Multi Processing Runtime Library Manual</a> has been updated and extended,
-      improving especially the description of <abbr title="internal control
-      variables">ICVs</abbr>, memory allocation, environment variables and OpenMP
-      routines. On Linux, <a href="https://github.com/numactl/numactl">libnuma</a>
-      is now used for allocators requesting the nearest-partition trait as
-      detailed in the manual.
-    </li>
   </ul>
   </li>
   <li id="openacc"><a href="https://gcc.gnu.org/wiki/OpenACC">OpenACC</a>

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

Summary of changes:
 htdocs/gcc-14/changes.html | 31 ++++++++++++++++---------------
 1 file changed, 16 insertions(+), 15 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2024-01-10  8:12 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=20240110081233.58DBB3858426@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).