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. a18af43b161b6ff4ea6e3aaf08dd72cbacb53a89 Date: Mon, 23 Jan 2023 08:56:26 +0000 (GMT) [thread overview] Message-ID: <20230123085626.611203858D32@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 a18af43b161b6ff4ea6e3aaf08dd72cbacb53a89 (commit) from c725ff4c2f62b43a5faa6488c3ff0030062b7ed6 (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 a18af43b161b6ff4ea6e3aaf08dd72cbacb53a89 Author: Tobias Burnus <tobias@codesourcery.com> Date: Mon Jan 23 09:55:18 2023 +0100 OpenMP: Update gcc-13/changes + projects/gomp * htdocs/gcc-13/changes.html: Improve wording; mention nvptx reverse offload; add 'some' to Fortran non-rect-loop support. * htdocs/projects/gomp/index.html: Split clause/directive entry for 'allocate' and mark the clause variant as fully implemented. Set Fortran non-rect-loop support back to partial. diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index ba42170c..6cd5dd64 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -59,12 +59,19 @@ a work-in-progress.</p> <li id="openmp"><a href="https://gcc.gnu.org/projects/gomp/">OpenMP</a> <ul> <li> - Reverse offload is now supported and the all clauses to the - <code>requires</code> directive are now accepted. However, the - <code>requires_offload</code>, <code>unified_address</code> - and <code>unified_shared_memory</code> clauses imply the initial - device (= the host) as the only available device. Fortran now - supports non-rectangular loop nests, which were added for C/C++ in GCC 11. + Reverse offload is now supported with nvptx devices. Additionally, the + <code>requires</code> handling has been improved and all clauses are + now accepted. If a requirement cannot be fulfilled for an accessible + device, this device is excluded from the list of available devices. This + may imply that the only device left is the host (the initial device). + In particular, <code>requires_offload</code> is currently unsupported on + AMD GCN devices while <code>unified_address</code> and + <code>unified_shared_memory</code> are unsupported by all non-host + devices. + </li> + <li> + OpenMP 5.0: Fortran now supports some non-rectangular loop nests; for + C/C++, the support was added in GCC 11. </li> <li> The following OpenMP 5.1 features have been added: the diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html index 19ff3c7d..17cf1ad9 100644 --- a/htdocs/projects/gomp/index.html +++ b/htdocs/projects/gomp/index.html @@ -372,8 +372,8 @@ than listed, depending on resolved corner cases and optimizations.</p> </tr> <tr> <td>Non-rectangular loop nests</td> - <td class="supported"><a href="../../gcc-11/changes.html#languages">GCC 11</a><br><a href="../../gcc-13/changes.html#languages">GCC 13</a></td> - <td>C/C++<br>Fortran</td> + <td class="partial"><a href="../../gcc-11/changes.html#languages">GCC 11</a><br><a href="../../gcc-13/changes.html#languages">GCC 13</a></td> + <td>C/C++ (full)<br>Fortran (partial)</td> </tr> <tr> <td>Nested-parallel changes to <em>max-active-levels-var</em> ICV</td> @@ -547,9 +547,14 @@ than listed, depending on resolved corner cases and optimizations.</p> <td></td> </tr> <tr> - <td><code>align</code> clause/modifier in <code>allocate</code> directive/clause and <code>allocator</code> directive</td> + <td><code>align</code> clause in <code>allocate</code> directive</td> + <td class="unsupported">No</td> + <td></td> + </tr> + <tr> + <td><code>align</code> modifier in <code>allocate</code> clause</td> <td class="supported"><a href="../../gcc-12/changes.html#languages">GCC 12</a></td> - <td>C/C++ on clause only</td> + <td></td> </tr> <tr> <td><code>thread_limit</code> clause to <code>target</code> construct</td> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/changes.html | 19 +++++++++++++------ htdocs/projects/gomp/index.html | 13 +++++++++---- 2 files changed, 22 insertions(+), 10 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-01-23 8:56 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=20230123085626.611203858D32@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).