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. 174d4dd6abf0c164f56a2149377979ed7eeeae1e Date: Mon, 6 Sep 2021 14:04:46 +0000 (GMT) [thread overview] Message-ID: <20210906140446.0F43A3858407@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 174d4dd6abf0c164f56a2149377979ed7eeeae1e (commit) from 11f6d53b2fba67011551c1be6399599c8b898d35 (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 174d4dd6abf0c164f56a2149377979ed7eeeae1e Author: Tobias Burnus <tobias@codesourcery.com> Date: Mon Sep 6 16:04:31 2021 +0200 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 ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-09-06 14: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=20210906140446.0F43A3858407@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: linkBe 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).