From: Thomas Schwinge <Thomas_Schwinge@mentor.com>
To: <andrew_stubbs@mentor.com>, <tobias_burnus@mentor.com>
Cc: Gerald Pfeifer <gerald@pfeifer.com>, <julian_brown@mentor.com>,
<gcc-patches@gcc.gnu.org>
Subject: RE: [wwwdocs] gcc-12/changes.html (GCN): >1 workers per gang
Date: Mon, 16 Aug 2021 11:28:17 +0200 [thread overview]
Message-ID: <87a6lhpwlq.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <d64cff46eeaf477cb650797f461c047d@svr-ies-mbx-01.mgc.mentorg.com>
Hi!
On 2021-08-16T10:34:34+0200, "Stubbs, Andrew" <Andrew_Stubbs@mentor.com> wrote:
>> In other words: For gangs > #CUs or >1 gang per CU, the following patch
>> is needed:
>> [OG11] https://gcc.gnu.org/g:4dcd1e1f4e6b451aac44f919b8eb3ac49292b308
>> [email] https://gcc.gnu.org/pipermail/gcc-patches/2020-July/550102.html
>> "not suitable for mainline until the multiple-worker support is merged
>> there"
>>
>> @Andrew + @Julian: Do you intent to commit it relatively soon?
>> Regarding the wwwdocs patch, I can hold off until that commit or reword
>> it to only cover the workers part.
>
> Were these not part of the patch set Thomas was working on?
That one is "amdgcn: Tune default OpenMP/OpenACC GPU utilization", which
indeed I'm planning to handle in the next few weeks. So I suggest we
simply hold back Tobias' 'gcc-12/changes.html' patch until that time.
Grüße
Thomas
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next prev parent reply other threads:[~2021-08-16 9:28 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 [this message]
2021-08-09 18:53 ` Gerald Pfeifer
2022-02-02 15:39 ` Tobias Burnus
2022-02-02 16:23 ` Andrew Stubbs
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=87a6lhpwlq.fsf@euler.schwinge.homeip.net \
--to=thomas_schwinge@mentor.com \
--cc=andrew_stubbs@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=julian_brown@mentor.com \
--cc=tobias_burnus@mentor.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).