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. 8324ef5943ff70ff1a7786f3d580be8cfe6edf99 Date: Mon, 16 Nov 2020 18:30:00 +0000 (GMT) [thread overview] Message-ID: <20201116183000.CD2963857C78@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 8324ef5943ff70ff1a7786f3d580be8cfe6edf99 (commit) from f7b7c18b437961e3d580708ff337e985212b30e2 (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 8324ef5943ff70ff1a7786f3d580be8cfe6edf99 Author: Tobias Burnus <tobias@codesourcery.com> Date: Mon Nov 16 19:28:43 2020 +0100 gcc-11/changes.html update for OpenMP + !GCC$ attributes + project/libgomp/ omp 5.1 update * htdocs/gcc-11/changes.html (OpenMP): Update. (Fortran): Add !GCC$ attributes DEPRECATED. * htdocs/projects/gomp/index.html: Add link to OpenMP 5.1. diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index 7f77268f..798257aa 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -124,12 +124,19 @@ a work-in-progress.</p> <ul> <li>GCC 11 adds support for non-rectangular loop nests in OpenMP constructs and the allocator routines of - <a href="https://www.openmp.org/specifications/">OpenMP 5.0</a>. + <a href="https://www.openmp.org/specifications/">OpenMP 5.0</a>, + including initial <code>allocate</code> clause support in C/C++. + The <code>OMP_TARGET_OFFLOAD</code> environment variable and the + active-levels routines are now supported. + For C/C++, the <code>declare variant</code> and <code>map</code> + support has been extended. For Fortran, OpenMP 4.5 is now fully supported and OpenMP 5.0 support has been extended, including the following features which were before only available in C and C++: <code>order(concurrent)</code>, - <code>device_type</code>, + <code>device_type</code>, memorder-clauses for <code>flush</code>, <code>lastprivate</code> with <code>conditional</code> modifier, + <code>atomic</code> construct and <code>reduction</code> clause + extensions of OpenMP 5.0, <code>if</code> clause with <code>simd</code> and <code>cancel</code> modifiers, <code>target data</code> without <code>map</code> clause, and limited support for the <code>requires</code> construct. @@ -222,7 +229,13 @@ a work-in-progress.</p> <!-- <h4 id="libstdcxx">Runtime Library (libstdc++)</h4> --> -<!-- <h3 id="fortran">Fortran</h3> --> +<h3 id="fortran">Fortran</h3> + +<ul> + <li>Added <code>DEPRECATED</code> to <code>!GCC$</code>'s + <code>attributes</code> directive. + </li> +</ul> <!-- <h3 id="go">Go</h3> --> diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html index 5be0938a..90e73175 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 13, 2020</b></dt> +<dd><p><a href="https://www.openmp.org/wp-content/uploads/OpenMP-API-Specification-5-1.pdf">OpenMP +Version 5.1</a> has been released.</p></dd> + <dt><b>August 20, 2020</b></dt> <dd><p><a href="https://www.openmp.org/wp-content/uploads/openmp-TR9.pdf">OpenMP Technical Report 9: Version 5.1 Public Comment Draft</a> has been released.</p></dd> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/changes.html | 19 ++++++++++++++++--- htdocs/projects/gomp/index.html | 4 ++++ 2 files changed, 20 insertions(+), 3 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-11-16 18:30 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=20201116183000.CD2963857C78@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).