From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/1] [fwprop]: Add the support of forwarding the vec_duplicate rtx
Date: Tue, 17 Jan 2023 15:37:58 -0700 [thread overview]
Message-ID: <a3e531eb-c40a-1bb9-a9b6-725c34387378@gmail.com> (raw)
In-Reply-To: <mpt3589rw06.fsf@arm.com>
On 1/17/23 09:00, Richard Sandiford via Gcc-patches wrote:
>
> But the idea of the fwprop change looks OK to me in principle.
> What we have now seems conservative, based on heuristics that
> haven't been updated in a long time. So relaxing them a bit seems
> like a good idea. IIRC Jeff had another case in which the current
> heuristics were too strict.
Two actually, though neither is relevant to this particular problem.
Jeff
next prev parent reply other threads:[~2023-01-17 22:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 9:42 lehua.ding
2023-01-13 10:59 ` juzhe.zhong
2023-01-17 16:00 ` Richard Sandiford
2023-01-17 22:37 ` Jeff Law [this message]
2023-01-18 0:49 ` 丁乐华
2023-01-18 9:07 ` Richard Sandiford
-- strict thread matches above, loose matches on Subject: below --
2023-01-13 9:14 lehua.ding
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=a3e531eb-c40a-1bb9-a9b6-725c34387378@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).