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. 4b4a85b696b3bb6700eea8f687bc45f1fd0b1f8c Date: Wed, 2 Feb 2022 17:52:32 +0000 (GMT) [thread overview] Message-ID: <20220202175232.EAF21385AC33@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 4b4a85b696b3bb6700eea8f687bc45f1fd0b1f8c (commit) from 56a010aa69b8ffe2fa8b6b2032173259950064f3 (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 4b4a85b696b3bb6700eea8f687bc45f1fd0b1f8c Author: Tobias Burnus <tobias@codesourcery.com> Date: Wed Feb 2 18:51:32 2022 +0100 gcc-12/changes.html (GCN): >1 workers per gang diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index 479bd6c5..b6341fda 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -360,6 +360,11 @@ a work-in-progress.</p> <li>Debug experience with ROCGDB has been improved.</li> <li>Support for the type <code>__int128_t</code>/<code>integer(kind=16)</code> was added.</li> + <li>For offloading, the limitation of using only one wavefront per compute + unit (CU) has been lifted. Up to 40 workgroups per CU and 16 wavefronts + per workgroup are supported (up to a limit of 40 wavefronts in total, + per CU). Additionally, the number of used wavefronts and workgroups was + tuned for performance.</li> </ul> <!-- <h3 id="arc">ARC</h3> --> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 5 +++++ 1 file changed, 5 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-02-02 17:52 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=20220202175232.EAF21385AC33@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).