From: Tobias Burnus <tobias@codesourcery.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>,
Gerald Pfeifer <gerald@pfeifer.com>,
Jakub Jelinek <jakub@redhat.com>
Subject: [wwwdocs] gcc-12/changes.html: OpenMP 5.1 update (was: [wwwdocs] gcc-12/changes.html: OpenMP - mention masked support)
Date: Mon, 6 Sep 2021 15:20:44 +0200 [thread overview]
Message-ID: <8c3348aa-9bac-5bfc-f4f1-a1e418cca351@codesourcery.com> (raw)
In-Reply-To: <f61c3571-5fbf-cb32-1fe9-2041ce721e98@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
On 13.08.21 16:37, Tobias Burnus wrote:
> Update the OpenMP section again, now that Jakub has added the 'masked'
> construct.
> Comments?
Jakub did comment on IRC that it probably makes sense to do less
frequent commits.
Thus, I waited a while and now have an update list. Besides 'masked' it
now mentions:
scope construct; nothing and error directive + primary in proc_bind.
OK? Comments? Suggestions?
Tobias
PS: Also new that the existing 'device' clause now supports the
modifiers 'device_num' and 'ancestor' and a bunch of bug fixes. While
very useful, I think those aren't changes.html worthy.
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
[-- Attachment #2: omp-mask-scope-error-nothing.diff --]
[-- Type: text/x-patch, Size: 2193 bytes --]
gcc-12/changes.html: OpenMP 5.1 update
* htdocs/gcc-12/changes.html (Caveats): Item about Fortran and omp_lib.h.
(OpenMP): More OMP 5.1 features: masked, scope, nothing, error + primary
in proc_bind.
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 06d5ea73..946faa49 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -31,6 +31,7 @@ a work-in-progress.</p>
<h2>Caveats</h2>
<ul>
<li>
+ <strong>C++:</strong>
Two non-standard <code>std::pair</code> constructors have been deprecated.
These allowed the use of an rvalue and a literal <code>0</code> to
construct a pair containing a move-only type and a pointer.
@@ -38,7 +39,14 @@ a work-in-progress.</p>
member instead of a literal <code>0</code>, as this is portable to other
C++ implementations.
</li>
- <li>...</li>
+ <li>
+ <strong>Fortran:</strong>
+ OpenMP code using the <code>omp_lib.h</code> include file can no longer be
+ compiled with <code>-std=f95</code> but now requires at least
+ <code>-std=f2003</code>. Alternatively, use the <code>omp_lib</code> module,
+ which still supports <code>-std=f95</code> and is recommended to be used
+ instead in general.
+ </li>
</ul>
@@ -57,8 +65,12 @@ a work-in-progress.</p>
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,
- support for expressing OpenMP directives as C++ 11 attributes has been
- added, which is an OpenMP 5.1 feature.
+ 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.
</li>
<li>The new warning flag <code>-Wopenacc-parallelism</code> was added for
OpenACC. It warns about potentially suboptimal choices related to
next prev parent reply other threads:[~2021-09-06 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 14:37 [wwwdocs] gcc-12/changes.html: OpenMP - mention masked support Tobias Burnus
2021-09-06 13:20 ` Tobias Burnus [this message]
2021-09-06 13:44 ` [wwwdocs] gcc-12/changes.html: OpenMP 5.1 update (was: [wwwdocs] gcc-12/changes.html: OpenMP - mention masked support) Jakub Jelinek
2023-01-16 23:42 ` [wwwdocs] gcc-12/changes.html: OpenMP - mention masked support Gerald Pfeifer
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=8c3348aa-9bac-5bfc-f4f1-a1e418cca351@codesourcery.com \
--to=tobias@codesourcery.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).