From: Jeff Law <jeffreyalaw@gmail.com>
To: Philipp Tomsich <philipp.tomsich@vrull.eu>, gcc-patches@gcc.gnu.org
Cc: Vineet Gupta <vineetg@rivosinc.com>,
Kito Cheng <kito.cheng@gmail.com>,
Jeff Law <jlaw@ventanamicro.com>,
Palmer Dabbelt <palmer@rivosinc.com>,
Christoph Muellner <christoph.muellner@vrull.eu>
Subject: Re: [PATCH] RISC-V: branch-(not)equals-zero compares against $zero
Date: Thu, 17 Nov 2022 15:44:31 -0700 [thread overview]
Message-ID: <41d536f8-0f5d-d7fa-1b9d-37d88ade6640@gmail.com> (raw)
In-Reply-To: <20221108195509.2701313-1-philipp.tomsich@vrull.eu>
On 11/8/22 12:55, Philipp Tomsich wrote:
> If we are testing a register or a paradoxical subreg (i.e. anything that is not
> a partial subreg) for equality/non-equality with zero, we can generate a branch
> that compares against $zero. This will work for QI, HI, SI and DImode, so we
> enable this for ANYI.
>
> 2020-08-30 gcc/ChangeLog:
>
> * config/riscv/riscv.md (*branch<mode>_equals_zero): Added pattern.
I've gone back an forth on this a few times. As you know, I hate
subregs in the target descriptions and I guess I need to extend that to
querying if something is a subreg or not rather than just subregs
appearing in the RTL.
Presumably the idea behind rejecting partial subregs is the bits outside
the partial is unspecified, but that's also going to be true if we're
looking at a hardreg in QImode (for example) irrespective of it being
wrapped in a subreg.
I don't doubt it works the vast majority of the time, but I haven't been
able to convince myself it'll work all the time. How do we ensure that
the bits outside the mode are zero? I've been bitten by this kind of
problem before, and it's safe to say it was exceedingly painful to find.
Jeff
next prev parent reply other threads:[~2022-11-17 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 19:55 Philipp Tomsich
2022-11-17 22:44 ` Jeff Law [this message]
2022-11-18 4:53 ` Palmer Dabbelt
2022-11-18 9:14 ` Philipp Tomsich
2022-11-19 16:47 ` 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=41d536f8-0f5d-d7fa-1b9d-37d88ade6640@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=christoph.muellner@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=jlaw@ventanamicro.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@rivosinc.com \
--cc=philipp.tomsich@vrull.eu \
--cc=vineetg@rivosinc.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).