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. dc1117ec1aa3d79ba24189275c19c88ab04d4dce
Date: Wed, 10 Nov 2021 11:32:46 +0000 (GMT)	[thread overview]
Message-ID: <20211110113246.C43763857C6A@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  dc1117ec1aa3d79ba24189275c19c88ab04d4dce (commit)
       via  8c4a1d2dc47954660de5c516cdda25b22977a4e8 (commit)
      from  e9738706a7754ced6165751d124b31183b025ff1 (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 dc1117ec1aa3d79ba24189275c19c88ab04d4dce
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Wed Nov 10 12:31:54 2021 +0100

    gcc-12/changes.html: Update OpenMP status

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 7d0c04f9..c40e275e 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -86,20 +86,36 @@ a work-in-progress.</p>
 <h2 id="languages">New Languages and Language specific improvements</h2>
 
 <ul>
-  <li>OpenMP 5.0 support has been extended: The <code>close</code> map modifier
+  <li>OpenMP
+  <ul>
+    <li>OpenMP 5.0 support has been extended: The <code>close</code> map modifier
       and the <code>affinity</code> clause are now supported and for Fortran
       additionally the following features which were available in C and C++
-      before:  <code>depobj</code>, <code>mutexinoutset</code> and
-       <code>iterator</code> can now also be used with the <code>depend</code>
-      clause, <code>defaultmap</code> has been updated for OpenMP 5.0, and the
-      <code>loop</code> directive and combined directives
-      involving <code>master</code> directive have been added. Additionally,
-      the following OpenMP 5.1 feature have been added: support for expressing
+      before: <code>declare variant</code> is now available,
+      <code>depobj</code>, <code>mutexinoutset</code> and <code>iterator</code>
+      can now also be used with the <code>depend</code> clause,
+      <code>defaultmap</code> has been updated for OpenMP 5.0, and the
+      <code>loop</code> directive and combined directives involving
+      <code>master</code> directive have been added.</li>
+    <li>The following OpenMP 5.1 feature have been added: support for expressing
       OpenMP directives as C++ 11 attributes, the <code>masked</code> and
       <code>scope</code> construct, the <code>nothing</code> and
       <code>error</code> directives, and using <code>primary</code> with the
       <code>proc_bind</code> clause and <code>OMP_PROC_BIND</code> environment
-      variable.
+      variable, the <code>reproducible</code> and <code>unconstrained</code>
+      modifiers to the <code>order</code> clause, and, for C/C++ only, the
+      align- and allocate-modifiers to the <code>allocate</code> clause and
+      the <code>atomic</code> extensions are now available. The
+      <code>OMP_PLACE</code> environment variable supports the OpenMP 5.1
+      features and the <code>OMP_NUM_TEAMS</code> and
+      <code>OMP_TEAMS_THREAD_LIMIT</code> environment variables and their
+      associated API routines are now supported as well as the memory-allocation
+      routines added for Fortran and extended for C/C++ in OpenMP 5.1. In
+      Fortran code, strictly-structured blocks can be used.</li>
+    <li>The <a
+      href="https://gcc.gnu.org/onlinedocs/libgomp/OpenMP-Implementation-Status.html"
+      >OpenMP Implementation Status</a> can be found in the libgomp manual.</li>
+  </ul>
   </li>
   <li>The new warning flag <code>-Wopenacc-parallelism</code> was added for
       OpenACC. It warns about potentially suboptimal choices related to

commit 8c4a1d2dc47954660de5c516cdda25b22977a4e8
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Wed Nov 10 12:30:04 2021 +0100

    projects/gomp/: Add OpenMP 5.2

diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html
index ff14b2b2..59697c10 100644
--- a/htdocs/projects/gomp/index.html
+++ b/htdocs/projects/gomp/index.html
@@ -69,6 +69,10 @@ available.</p>
 
 <h2>Status</h2>
 <dl>
+<dt><b>November 9, 2021</b></dt>
+<dd><p><a href="https://www.openmp.org/wp-content/uploads/OpenMP-API-Specification-5-2.pdf">OpenMP
+Version 5.2</a> has been released.</p></dd>
+
 <dt><b>July 15, 2021</b></dt>
 <dd><p><a href="https://www.openmp.org/wp-content/uploads/openmp-TR10.pdf">OpenMP
 Technical Report 10: Version 5.2 Public Comment Draft</a> has been released.</p></dd>

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

Summary of changes:
 htdocs/gcc-12/changes.html      | 32 ++++++++++++++++++++++++--------
 htdocs/projects/gomp/index.html |  4 ++++
 2 files changed, 28 insertions(+), 8 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2021-11-10 11:32 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=20211110113246.C43763857C6A@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).