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. 5392ce3e27d9a852c3375ecf5d3be19561c00b51 Date: Thu, 14 Dec 2023 13:50:53 +0000 (GMT) [thread overview] Message-ID: <20231214135053.7A1BA3858D20@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 5392ce3e27d9a852c3375ecf5d3be19561c00b51 (commit) from 617a25d7d89a9cce121e85b693eed1ee3f94354b (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 5392ce3e27d9a852c3375ecf5d3be19561c00b51 Author: Tobias Burnus <tobias@codesourcery.com> Date: Thu Dec 14 14:50:18 2023 +0100 gcc-14/changes.html + project/gomp/: Update OpenMP status diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index 6d7138f8..346785a0 100644 --- a/htdocs/gcc-14/changes.html +++ b/htdocs/gcc-14/changes.html @@ -52,10 +52,22 @@ a work-in-progress.</p> <li> The <code>requires</code> directive's <code>unified_address</code> requirement is now fulfilled by both AMD GCN and nvptx devices. + AMD GCN and nvptx devices now support low-latency allocators as + <a href="https://gcc.gnu.org/onlinedocs/libgomp/Offload-Target-Specifics.html" + >detailed in the manual</a>. Initial support for pinned-memory + allocators has been added (<a href="https://gcc.gnu.org/onlinedocs/libgomp/Memory-allocation.html" + >as detailed in the manual</a>) </li> <li>OpenMP 5.0: The <code>allocate</code> directive is now supported for stack variables in C and Fortran, including the OpenMP 5.1 - <code>align</code> modifier. + <code>align</code> modifier. For Fortran, OpenMP allocators can now be + used for allocatables and pointers using the <code>allocate</code> + directive and its OpenMP 5.2 replacement, the <code>allocators</code> + directive; files using this allocator and all files that might directly + or indirectly (intrinisic assignment, <code>intent(out)</code>, ...) + de- or reallocate such-allocated variables must be compiled with the + <a href="https://gcc.gnu.org/onlinedocs/gfortran/Fortran-Dialect-Options.html#index-fopenmp-allocators" + ><code>-fopenmp-allocators</code></a> option. </li> <li> OpenMP 5.1: Support was added for collapsing imperfectly nested loops and diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html index 03f74a88..bf20bb88 100644 --- a/htdocs/projects/gomp/index.html +++ b/htdocs/projects/gomp/index.html @@ -480,7 +480,7 @@ than listed, depending on resolved corner cases and optimizations.</p> <tr> <td><code>allocate</code> directive</td> <td class="partial"><a href="../../gcc-14/changes.html#languages">GCC 14</a></td> - <td>Only C and Fortran, only stack variables</td> + <td>Only C for stack/automatic and Fortran for stack/automatic and allocatable/pointer variables</td> </tr> <tr> <td>Discontiguous array section with <code>target update</code> construct</td> @@ -555,7 +555,7 @@ than listed, depending on resolved corner cases and optimizations.</p> <tr> <td><code>align</code> clause in <code>allocate</code> directive</td> <td class="partial"><a href="../../gcc-14/changes.html#languages">GCC 14</a></td> - <td>Only C and Fortran (and only stack variables)</td> + <td>Only C and Fortran (and not for static variables)</td> </tr> <tr> <td><code>align</code> modifier in <code>allocate</code> clause</td> @@ -820,10 +820,15 @@ than listed, depending on resolved corner cases and optimizations.</p> <td></td> </tr> <tr> - <td>Deprecation of no-argument <code>destroy</code> clause on <code>depobj</code></td> + <td><code>destroy</code> clause with <em>destroy-var</em> argument on <code>depobj</code></td> <td class="supported"><a href="../../gcc-14/changes.html#languages">GCC 14</a></td> <td></td> </tr> + <tr> + <td>Deprecation of no-argument <code>destroy</code> clause on <code>depobj</code></td> + <td class="unsupported">No</td> + <td></td> + </tr> <tr> <td><code>linear</code> clause syntax changes and <code>step</code> modifier</td> <td class="supported"><a href="../../gcc-13/changes.html#languages">GCC 13</a></td> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-14/changes.html | 14 +++++++++++++- htdocs/projects/gomp/index.html | 11 ++++++++--- 2 files changed, 21 insertions(+), 4 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-12-14 13:50 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=20231214135053.7A1BA3858D20@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).