public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. c6a7f816f3531d5727674620d74818fe1d150467
Date: Fri,  6 May 2022 09:04:41 +0000 (GMT)	[thread overview]
Message-ID: <20220506090442.049EA385625C@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  c6a7f816f3531d5727674620d74818fe1d150467 (commit)
      from  23371fde6d881e87c6cefbe2f5f55dfacfb508df (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 c6a7f816f3531d5727674620d74818fe1d150467
Author: Thomas Schwinge <thomas@codesourcery.com>
Date:   Fri May 6 11:03:13 2022 +0200

    GCC 12: OpenACC

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 1b6385cd..c64827bd 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -170,9 +170,38 @@ You may also want to check out our
       >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
-      OpenACC parallelism.
+  <li id="openacc">
+    Version 2.6 of the <a href="https://www.openacc.org/">OpenACC</a>
+    specification continues to be maintained and improved in the C, C++ and
+    Fortran compilers.
+    See the <a href="https://gcc.gnu.org/wiki/OpenACC/Implementation%20Status#status-12">implementation
+    status</a> section on the OpenACC wiki page and the
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-12.1.0/libgomp/Enabling-OpenACC.html">
+    run-time library documentation</a> for further information.
+    In addition to general performance tuning and bug fixing, new features
+    include:
+    <ul>
+      <li>
+	OpenACC worker parallelism for <a href="#amdgcn">AMD GPUs</a>
+	(already for a long time supported for <a href="#nvptx">Nvidia
+	GPUs</a>).
+      </li>
+      <li>
+	Data privatization/sharing at the OpenACC gang level.
+      </li>
+      <li>
+	Considerable improvements for the experimental OpenACC 'kernels'
+	decomposition
+	(<a href="https://gcc.gnu.org/onlinedocs/gcc-12.1.0/gcc/Optimize-Options.html#index-param"><code>--param
+	openacc-kernels=decompose</code></a>).
+      </li>
+      <li>
+	A new warning
+	flag <a href="https://gcc.gnu.org/onlinedocs/gcc-12.1.0/gcc/Warning-Options.html#index-Wopenacc-parallelism"><code>-Wopenacc-parallelism</code></a>
+	to warn about potentially suboptimal choices related to OpenACC
+	parallelism.
+      </li>
+    </ul>
   </li>
   <li>The offload target code generation for OpenMP and OpenACC can now
       be better adjusted using the new <a

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

Summary of changes:
 htdocs/gcc-12/changes.html | 35 ++++++++++++++++++++++++++++++++---
 1 file changed, 32 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2022-05-06  9:04 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=20220506090442.049EA385625C@sourceware.org \
    --to=tschwinge@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).