From: Richard Sandiford <richard.sandiford@arm.com>
To: Steve Ellcey <sellcey@marvell.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch 1/4][Aarch64] v2: Implement Aarch64 SIMD ABI
Date: Wed, 12 Dec 2018 11:39:00 -0000 [thread overview]
Message-ID: <87woofas9w.fsf@arm.com> (raw)
In-Reply-To: <5215c53c2e14b1b1980fe4294516b2eea0053391.camel@marvell.com> (Steve Ellcey's message of "Tue, 11 Dec 2018 23:01:25 +0000")
Steve Ellcey <sellcey@marvell.com> writes:
> On Fri, 2018-12-07 at 17:34 +0000, Richard Sandiford wrote:
>> > + (match_operand:TX 2 "register_operand" "w"))
>> > + (set (mem:TX (plus:P (match_dup 0)
>> > + (match_operand:P 5 "const_int_operand" "n")))
>> > + (match_operand:TX 3 "register_operand" "w"))])]
>>
>> Think this last part should be:
>>
>> (set (mem:TX (plus:P (plus:P (match_dup 0)
>> (match_dup 4))
>> (match_operand:P 5 "const_int_operand"
>> "n")))
>> (match_operand:TX 3 "register_operand" "w"))])]
>
> I think you are right about this. What I have for
> loadwb_pair<TX:mode>_<P:mode> matches what is there for
> loadwb_pair<GPF:mode>_<P:mode>. If this one is wrong, then I assume
> the others are wrong too? This won't make a practical difference since
> we call these with gen_loadwb_pair*_* calls and not via pattern
> recognition, but still they should be right. Should I change them
> all? I did not change this as part of this patch.
I think we should fix the new pattern, but I agree fixing the others
should be a separate patch.
Patch LGTM with that change.
Thanks,
Richard
next prev parent reply other threads:[~2018-12-12 11:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 17:52 Steve Ellcey
2018-12-07 17:34 ` Richard Sandiford
2018-12-11 23:01 ` Steve Ellcey
2018-12-12 11:39 ` Richard Sandiford [this message]
2018-12-12 18:26 ` [EXT] " Steve Ellcey
2018-12-12 18:49 ` Richard Sandiford
2019-02-13 16:54 ` Szabolcs Nagy
2019-02-13 17:24 ` Steve Ellcey
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=87woofas9w.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=sellcey@marvell.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).