From: Vladimir Makarov <vmakarov@redhat.com>
To: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Subject: Re: [PATCH] lra: Updates of biggest mode for hard regs [PR112278]
Date: Mon, 4 Dec 2023 15:15:37 -0500 [thread overview]
Message-ID: <8993908a-e12b-d50c-50ae-c994b926b3a5@redhat.com> (raw)
In-Reply-To: <mpt7clva91r.fsf@arm.com>
On 12/3/23 05:13, Richard Sandiford wrote:
> [Gah. In my head I'd sent this a few weeks ago, but it turns out
> that I hadn't even got to the stage of writing the changlog...]
>
> LRA keeps track of the biggest mode for both hard registers and
> pseudos. The updates assume that the modes are ordered, i.e. that
> we can tell whether one is no bigger than the other at compile time.
>
> That is (or at least seemed to be) a reasonable restriction for pseudos.
> But it isn't necessarily so for hard registers, since the uses of hard
> registers can be logically distinct. The testcase is an example of this.
>
> The biggest mode of hard registers is also special for other reasons.
> As the existing comment says:
>
> /* A reg can have a biggest_mode of VOIDmode if it was only ever seen as
> part of a multi-word register. In that case, just use the reg_rtx
> mode. Do the same also if the biggest mode was larger than a register
> or we can not compare the modes. Otherwise, limit the size to that of
> the biggest access in the function or to the natural mode at least. */
>
> This patch applies the same approach to the updates.
>
> Tested on aarch64-linus-gnu (with and without SVE) and on x86_64-linux-gnu.
> OK to install?
>
Sure. Thank you for fixing this, Richard.
prev parent reply other threads:[~2023-12-04 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 10:13 Richard Sandiford
2023-12-04 20:15 ` Vladimir Makarov [this message]
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=8993908a-e12b-d50c-50ae-c994b926b3a5@redhat.com \
--to=vmakarov@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.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).