public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard.sandiford@arm.com>
To: Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>
Cc: gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Missed lowering to ld1rq from svld1rq for memory operand
Date: Fri, 05 Aug 2022 13:19:03 +0100	[thread overview]
Message-ID: <mpth72qnars.fsf@arm.com> (raw)
In-Reply-To: <CAAgBjM=5ELyC+e3McMiaS--hiaR1yqxzKqvT3466XGBQjC_jig@mail.gmail.com> (Prathamesh Kulkarni's message of "Fri, 5 Aug 2022 17:02:22 +0530")

Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org> writes:
> Hi Richard,
> Following from off-list discussion, in the attached patch, I wrote pattern
> similar to vec_duplicate<mode>_reg, which seems to work for the svld1rq tests.
> Does it look OK ?
>
> Sorry, I didn't fully understand your suggestion on integrating with
> vec_duplicate<mode>_reg
> pattern. For vec_duplicate<mode>_reg, the operand to vec_duplicate expects
> mode to be <VEL>, while the pattern in patch expects operand of
> vec_duplicate to have mode <V128>.
> How do we write a pattern so an operand can accept either of the 2 modes ?

I quoted the wrong one, sorry, should have been
aarch64_vec_duplicate_vq<mode>_le.

> Also it seems <V128> cannot be used with SVE_ALL ?

Yeah, these would be SVE_FULL only.

Richard


  reply	other threads:[~2022-08-05 12:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05 11:32 Prathamesh Kulkarni
2022-08-05 12:19 ` Richard Sandiford [this message]
2023-01-10 17:34   ` Prathamesh Kulkarni
2023-01-12 15:32     ` Richard Sandiford
2023-01-14 17:59       ` Prathamesh Kulkarni

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=mpth72qnars.fsf@arm.com \
    --to=richard.sandiford@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=prathamesh.kulkarni@linaro.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).