From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [RFA] Avoid unnecessary load-immediate in coremark
Date: Sat, 1 Oct 2022 12:58:11 -0600 [thread overview]
Message-ID: <4e31f6ce-9e69-852b-6c0d-161fd9c0d0aa@gmail.com> (raw)
In-Reply-To: <CAFiYyc3WNY-rchLLpz7ep07XQBLe=GXr6HMZshk5LoJqqdY5jA@mail.gmail.com>
On 9/29/22 01:44, Richard Biener wrote:
> On Tue, Sep 27, 2022 at 9:54 PM Jeff Law <jlaw@ventanamicro.com> wrote:
>>
>> This is another minor improvement to coremark. I suspect this only
>> improves code size as the load-immediate was likely issuing with the ret
>> statement on multi-issue machines.
>>
>>
>> Basically we're failing to utilize conditional equivalences during the
>> post-reload CSE pass. So if a particular block is only reached when a
>> certain condition holds (say for example a4 == 0) and the block has an
>> assignment like a4 = 0, we would fail to eliminate the unnecessary
>> assignment.
> conditional equivalences on RTL - ick ;)
That was my first reaction as well.
>
> I'm not familiar with RTL pattern matching so somebody else has to
> comment on that, but
>
> + /* If this is not the first time through, then
> + verify the source and destination match. */
> + else if (dest == XEXP (cond, 0) && src == XEXP (cond, 1))
> + ;
>
> shouldn't you restrict dest/src somehow? It might be a MEM?
> The way you create the fake insn suggests only REG_P dest are OK
> (not SUBREGs for example?)?
You're absolutely right, as is Richard S WRT unexpected sharing. I'll
adjust the patch appropriately.
> Should you use rtx_equal_p (not using that possibly exempts MEM,
> but being more explicit would be nice). Should you restrict this to
> MODE_INT compares?
rtx_equal_p would be better, yes. I'll adjust that too.
This should work regardless of hte mode type though. The key is the
post-reload cse bits have to check that the pattern matches and that the
constraints are satisfied when a replacement is made. My only concern
would be MODE_CC stuff. I'll think a bit more about that case.
Jeff
next prev parent reply other threads:[~2022-10-01 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 19:53 Jeff Law
2022-09-29 7:44 ` Richard Biener
2022-10-01 18:58 ` Jeff Law [this message]
2022-09-30 10:47 ` Richard Sandiford
2022-10-01 19:03 ` Jeff Law
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=4e31f6ce-9e69-852b-6c0d-161fd9c0d0aa@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@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).