From: Jeff Law <law@redhat.com>
To: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Subject: Re: New .md construct: define_insn_and_rewrite
Date: Mon, 20 May 2019 19:47:00 -0000 [thread overview]
Message-ID: <e13429de-3582-9c2a-ef47-c9b0f95a4ec9@redhat.com> (raw)
In-Reply-To: <mptlfz9jf7b.fsf@arm.com>
On 5/14/19 8:14 AM, Richard Sandiford wrote:
> Several SVE patterns need define_insn_and_splits that generate the
> same insn_code, but with different operands. That's probably a
> niche requirement, but it's cropping up often enough on the ACLE
> branch that I think it would be good to have a syntactic sugar for it.
>
> This patch therefore adds a new construct called define_insn_and_rewrite.
> It's basically a define_insn_and_split with an implicit split pattern,
> obtained by copying the insn pattern and replacing match_operands with
> match_dups and match_operators with match_op_dups.
>
> Any comments? Suggestions for better names?
No strong opinions here other than to mention that I think there's other
places we could use this.
Jeff
prev parent reply other threads:[~2019-05-20 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 14:14 Richard Sandiford
2019-05-14 16:56 ` Eric Botcazou
2019-05-15 6:48 ` Richard Sandiford
2019-05-19 1:45 ` Hans-Peter Nilsson
2019-05-31 16:46 ` Richard Sandiford
2019-05-20 19:47 ` Jeff Law [this message]
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=e13429de-3582-9c2a-ef47-c9b0f95a4ec9@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.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).