public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Stubbs, Andrew" <Andrew_Stubbs@mentor.com>
To: "Burnus, Tobias" <Tobias_Burnus@mentor.com>,
	"Schwinge, Thomas" <Thomas_Schwinge@mentor.com>,
	Gerald Pfeifer <gerald@pfeifer.com>,
	"Brown, Julian" <Julian_Brown@mentor.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: [wwwdocs] gcc-12/changes.html (GCN): >1 workers per gang
Date: Mon, 16 Aug 2021 08:34:34 +0000	[thread overview]
Message-ID: <d64cff46eeaf477cb650797f461c047d@svr-ies-mbx-01.mgc.mentorg.com> (raw)
In-Reply-To: <69870f64-b4e2-2f4c-8431-cff45c631cb2@codesourcery.com>

> 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?

Andrew

  reply	other threads:[~2021-08-16  8:34 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 [this message]
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
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=d64cff46eeaf477cb650797f461c047d@svr-ies-mbx-01.mgc.mentorg.com \
    --to=andrew_stubbs@mentor.com \
    --cc=Julian_Brown@mentor.com \
    --cc=Thomas_Schwinge@mentor.com \
    --cc=Tobias_Burnus@mentor.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.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).