From: Jeff Law <jeffreyalaw@gmail.com>
To: Robin Dapp <rdapp.gcc@gmail.com>,
Vineet Gupta <vineetg@rivosinc.com>,
gcc-patches@gcc.gnu.org
Cc: gnu-toolchain@rivosinc.com
Subject: Re: [RFC] RISC-V: elide sign extend when expanding cmp_and_jump
Date: Wed, 25 Oct 2023 07:52:01 -0600 [thread overview]
Message-ID: <7c049504-b8f7-4f03-aa54-5015c74d1bbe@gmail.com> (raw)
In-Reply-To: <20af64b0-2c3b-426e-adc0-10baac70e7f7@gmail.com>
On 10/25/23 07:47, Robin Dapp wrote:
>
>> Well, it doesn't seem like there's a lot of difference between doing
>> it in the generic expander bits vs target expander bits -- the former
>> just calls into the latter for the most part. Thus if the
>> subreg-promoted state is available in the target expander, I'd expect
>> it to be available in the generic expander.
>
> Ah, sorry I meant in the [sign|zero]extend expanders rather than the
> compare expanders in order to catch promoted subregs from other origins
> as well. Maybe that doesn't work, though?
That's a *really* interesting idea. Interested in playing around a bit
with that Vineet?
jeff
next prev parent reply other threads:[~2023-10-25 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 5:01 Vineet Gupta
2023-10-25 7:12 ` Robin Dapp
2023-10-25 13:32 ` Jeff Law
2023-10-25 13:47 ` Robin Dapp
2023-10-25 13:52 ` Jeff Law [this message]
2023-10-25 16:37 ` Vineet Gupta
2023-10-25 16:25 ` Vineet Gupta
2023-10-25 16:30 ` Jeff Law
2023-10-25 16:31 ` Vineet Gupta
2023-10-25 23:28 ` Vineet Gupta
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=7c049504-b8f7-4f03-aa54-5015c74d1bbe@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=rdapp.gcc@gmail.com \
--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).