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. 324b81b41b986d0b77752209b6e3767d708893ad Date: Thu, 23 Feb 2023 14:41:13 +0000 (GMT) [thread overview] Message-ID: <20230223144113.66A733858C00@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 324b81b41b986d0b77752209b6e3767d708893ad (commit) from 8edbd72f42afcfc7c92099b9feaf42e5f0ccf11b (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 324b81b41b986d0b77752209b6e3767d708893ad Author: Tobias Burnus <tobias@codesourcery.com> Date: Thu Feb 23 15:40:16 2023 +0100 OpenMP update for gcc-13/changes.html + projects/gomp/ diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index 6034a8f9..a803f501 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -69,13 +69,13 @@ 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 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 + Reverse offload is now supported with AMD GCN and 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>unified_address</code> and <code>unified_shared_memory</code> are unsupported by all non-host devices. </li> diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html index b2b3b0c8..3ef4f502 100644 --- a/htdocs/projects/gomp/index.html +++ b/htdocs/projects/gomp/index.html @@ -315,8 +315,8 @@ than listed, depending on resolved corner cases and optimizations.</p> <td> (<code>atomic_default_mem_order</code>)<br> (<code>dynamic_allocators</code>)<br> - complete but no non-host devices provides <code>unified_address</code>, - <code>unified_shared_memory</code> or <code>reverse_offload</code> + complete but no non-host devices provides <code>unified_address</code> or + <code>unified_shared_memory</code> </td> </tr> <tr> @@ -432,7 +432,7 @@ than listed, depending on resolved corner cases and optimizations.</p> </td> <td> Reverse offload unsupported<br> - See comment for <code>requires</code> + Reverse offload supported</code> </td> </tr> <tr> @@ -1062,8 +1062,7 @@ error.</p> <td></td> </tr> <tr> - <td><code>strict</code> modifier keyword to <code>num_threads</code>, <code>num_tasks</code> - and <code>grainsize</code> + <td><code>strict</code> modifier keyword to <code>num_threads</code> <td class="unsupported">No</td> <td></td> </tr> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/changes.html | 14 +++++++------- htdocs/projects/gomp/index.html | 9 ++++----- 2 files changed, 11 insertions(+), 12 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-02-23 14:41 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=20230223144113.66A733858C00@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).