From: Richard Sandiford <richard.sandiford@arm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Jeff Law via Gcc-patches <gcc-patches@gcc.gnu.org>,
Tamar Christina <Tamar.Christina@arm.com>,
Roger Sayle <roger@nextmovesoftware.com>,
Jeff Law <jeffreyalaw@gmail.com>
Subject: Re: [PATCH] combine: Try harder to form zero_extends [PR106594]
Date: Mon, 06 Mar 2023 15:08:00 +0000 [thread overview]
Message-ID: <mptv8jd9aun.fsf@arm.com> (raw)
In-Reply-To: <20230306135850.GN25951@gate.crashing.org> (Segher Boessenkool's message of "Mon, 6 Mar 2023 07:58:50 -0600")
Segher Boessenkool <segher@kernel.crashing.org> writes:
> On Mon, Mar 06, 2023 at 12:47:06PM +0000, Richard Sandiford wrote:
>> How about the patch below?
>
> What about it? What would make it any better than the previous?
It does what Jeff suggested in the quoted message: work within the existing
extract/make_compound_operation scheme rather than try to opt out of it.
Richard
next prev parent reply other threads:[~2023-03-06 15:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 18:32 [PATCH] PR rtl-optimization/106594: Preserve zero_extend in combine when cheap Roger Sayle
2023-03-04 22:17 ` Segher Boessenkool
2023-03-05 19:28 ` Tamar Christina
2023-03-05 19:56 ` Jeff Law
2023-03-05 20:43 ` Tamar Christina
2023-03-05 21:33 ` Segher Boessenkool
2023-03-06 12:08 ` Segher Boessenkool
2023-03-06 12:11 ` Tamar Christina
2023-03-06 12:47 ` [PATCH] combine: Try harder to form zero_extends [PR106594] Richard Sandiford
2023-03-06 13:58 ` Segher Boessenkool
2023-03-06 15:08 ` Richard Sandiford [this message]
2023-03-06 16:18 ` Jakub Jelinek
2023-03-06 16:34 ` Richard Sandiford
2023-03-06 18:31 ` Segher Boessenkool
2023-03-06 19:13 ` Richard Sandiford
2023-03-06 23:31 ` Segher Boessenkool
2023-03-08 11:58 ` Richard Sandiford
2023-03-08 22:50 ` Segher Boessenkool
2023-03-09 10:18 ` Richard Sandiford
2023-03-06 22:58 ` Segher Boessenkool
2023-03-06 18:13 ` Segher Boessenkool
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=mptv8jd9aun.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=Tamar.Christina@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=roger@nextmovesoftware.com \
--cc=segher@kernel.crashing.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).