Hans-Peter Nilsson writes:
> On Tue, 14 May 2019, 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 t
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 syn
On Tue, 14 May 2019, 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 sy
Eric Botcazou writes:
>> 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_dup
> 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.
Isn't that what define_
