public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Stubbs <ams@codesourcery.com>
To: Tobias Burnus <tobias@codesourcery.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	Gerald Pfeifer <gerald@pfeifer.com>,
	Thomas Schwinge <thomas@codesourcery.com>
Subject: Re: [wwwdocs] gcc-12/changes.html (GCN): >1 workers per gang
Date: Wed, 2 Feb 2022 16:23:31 +0000	[thread overview]
Message-ID: <4364eaef-d446-eac6-17ed-6736075658ba@codesourcery.com> (raw)
In-Reply-To: <610ab036-8d0d-c9a9-8010-7825f8fb97dd@codesourcery.com>

On 02/02/2022 15:39, Tobias Burnus wrote:
> On 09.08.21 15:55, Tobias Burnus wrote:
>> Now that the GCN/OpenACC patches for this have been committed today,
>> I think it makes sense to add it to the documentation.
>> (I was told that some follow-up items are still pending, but as
>> the feature does work ...)
> 
> I think the follow-up patches have now been committed.
> How about the attached patch?

We should probably add a qualification "(up to a limit of 40 wavefronts 
in total, per CU)" or else were suggesting that there can be 40 
workgroups of 16 wavefronts, which the hardware will not do.

Andrew

  reply	other threads:[~2022-02-02 16:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09 13:55 Tobias Burnus
2021-08-09 14:27 ` Thomas Schwinge
2021-08-10 10:10   ` Tobias Burnus
2021-08-16  8:34     ` Stubbs, Andrew
2021-08-16  9:28       ` Thomas Schwinge
2021-08-09 18:53 ` Gerald Pfeifer
2022-02-02 15:39 ` Tobias Burnus
2022-02-02 16:23   ` Andrew Stubbs [this message]
2022-02-02 17:54     ` Tobias Burnus

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=4364eaef-d446-eac6-17ed-6736075658ba@codesourcery.com \
    --to=ams@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=thomas@codesourcery.com \
    --cc=tobias@codesourcery.com \
    /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: link
Be 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).