From: Tobias Burnus <tobias@codesourcery.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>,
Gerald Pfeifer <gerald@pfeifer.com>,
Jakub Jelinek <jakub@redhat.com>,
Andrew Stubbs <andrew_stubbs@mentor.com>
Subject: [wwwdocs] gcc-12/changes.html: OpenMP + GCN update
Date: Wed, 23 Jun 2021 11:53:44 +0200 [thread overview]
Message-ID: <c6e01061-6df1-d699-eb1e-4cc816d33f14@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
Hi all,
this patch updates OpenMP for the non-bug-fix commits which have
been done in the last weeks.
It also updates GCN. The change assumes that the just approved
patch is committed ...
Comments, thoughts, wording suggestions? Did I miss some commit/feature?
Tobias
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstrasse 201, 80634 München Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Frank Thürauf
[-- Attachment #2: wwdocs.diff --]
[-- Type: text/x-patch, Size: 1783 bytes --]
gcc-12/changes.html: OpenMP + GCN update
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 07f70b8b..b854c4e6 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -49,10 +49,14 @@ a work-in-progress.</p>
<h2 id="languages">New Languages and Language specific improvements</h2>
<ul>
- <li>OpenMP 5.0 support for Fortran has been extended by the following features
- which were available in C and C++ before: <code>depobj</code>
- and <code>mutexinoutset</code> can now also be used with the
- <code>depend</code> clause.
+ <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.
</li>
<li>The new warning flag <code>-Wopenacc-parallelism</code> was added for
OpenACC. It warns about potentially suboptimal choices related to
@@ -97,14 +101,17 @@ a work-in-progress.</p>
<!-- <h3 id="aarch64">AArch64</h3> -->
+<h3 id="amdgcn">AMD Radeon (GCN)</h3>
+<ul>
+ <li>Debug experience with ROCGDB has been improved.</li>
+</ul>
+
<!-- <h3 id="arc">ARC</h3> -->
<!-- <h3 id="arm">ARM</h3> -->
<!-- <h3 id="avr">AVR</h3> -->
-<!-- <h3 id="hsa">Heterogeneous Systems Architecture</h3> -->
-
<!-- <h3 id="x86">IA-32/x86-64</h3> -->
<!-- <h3 id="mips">MIPS</h3> -->
next reply other threads:[~2021-06-23 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 9:53 Tobias Burnus [this message]
2021-06-23 9:58 ` Andrew Stubbs
2021-06-28 9:47 ` Tobias Burnus
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=c6e01061-6df1-d699-eb1e-4cc816d33f14@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=andrew_stubbs@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jakub@redhat.com \
/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).