From: Chung-Lin Tang <chunglin.tang@siemens.com>
To: Andrew Stubbs <ams@codesourcery.com>, gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Register allocation cost question
Date: Wed, 11 Oct 2023 14:54:20 +0800 [thread overview]
Message-ID: <8cc599b6-1037-4946-b88a-12a8ebc7cc00@siemens.com> (raw)
In-Reply-To: <9c350ebd-fd67-4975-abee-68787f97c383@codesourcery.com>
On 2023/10/10 11:11 PM, Andrew Stubbs wrote:
> Hi all,
>
> I'm trying to add a new register set to the GCN port, but I've hit a
> problem I don't understand.
>
> There are 256 new registers (each 2048 bit vector register) but the
> register file has to be divided between all the running hardware
> threads; if you can use fewer registers you can get more parallelism,
> which means that it's important that they're allocated in order.
>
> The problem is that they're not allocated in order. Somehow the IRA pass
> is calculating different costs for the registers within the class. It
> seems to prefer registers a32, a96, a160, and a224.
>
> The internal regno are 448, 512, 576, 640. These are not random numbers!
> They all have zero for the 6 LSB.
>
> What could cause this? Did I overrun some magic limit? What target hook
> might I have miscoded?
>
> I'm also seeing wrong-code bugs when I allow more than 32 new registers,
> but that might be an unrelated problem. Or the allocation is broken? I'm
> still analyzing this.
>
> If it matters, ... the new registers can't be used for general purposes,
> so I'm trying to set them up as a temporary spill destination. This
> means they're typically not busy. It feels like it shouldn't be this
> hard... :(
Have you tried experimenting with REG_ALLOC_ORDER? I see that the GCN port currently isn't using this target macro.
Chung-Lin
next prev parent reply other threads:[~2023-10-11 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 15:11 Andrew Stubbs
2023-10-10 19:09 ` Segher Boessenkool
2023-10-11 8:57 ` Andrew Stubbs
2023-10-11 14:49 ` Andrew Stubbs
2023-10-11 6:54 ` Chung-Lin Tang [this message]
2023-10-11 8:58 ` Andrew Stubbs
2023-10-11 10:56 ` Richard Earnshaw (lists)
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=8cc599b6-1037-4946-b88a-12a8ebc7cc00@siemens.com \
--to=chunglin.tang@siemens.com \
--cc=ams@codesourcery.com \
--cc=gcc@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: 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).