From: Richard Sandiford <richard.sandiford@arm.com>
To: Tejas Belagod <Tejas.Belagod@arm.com>
Cc: "gcc-patches\@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] [PR96339] AArch64: Optimise svlast[ab]
Date: Fri, 19 May 2023 10:50:04 +0100 [thread overview]
Message-ID: <mpt5y8oveer.fsf@arm.com> (raw)
In-Reply-To: <AS8PR08MB7079885BE6ABA5593B9F7F70EA7C9@AS8PR08MB7079.eurprd08.prod.outlook.com> (Tejas Belagod's message of "Fri, 19 May 2023 10:08:12 +0100")
Tejas Belagod <Tejas.Belagod@arm.com> writes:
> Am I correct to understand that we still need to check for the case when
> there's a repeating non-zero elements in the case of NELTS_PER_PATTERN == 2?
> eg. { 0, 0, 1, 1, 1, 1,....} which should be encoded as {0, 0, 1, 1} with
> NPATTERNS = 2 ?
Yeah, that's right. The current handling for NPATTERNS==2 looked
good to me. It was the other two cases that I was worried about.
Thanks,
Richard
next prev parent reply other threads:[~2023-05-19 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 11:39 Tejas Belagod
2023-05-04 5:43 ` Tejas Belagod
2023-05-11 19:32 ` Richard Sandiford
2023-05-16 8:03 ` Tejas Belagod
2023-05-16 8:45 ` Richard Sandiford
2023-05-16 11:28 ` Tejas Belagod
2023-05-16 12:06 ` Richard Sandiford
2023-05-19 9:08 ` Tejas Belagod
2023-05-19 9:50 ` Richard Sandiford [this message]
2023-06-12 8:31 ` Tejas Belagod
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=mpt5y8oveer.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=Tejas.Belagod@arm.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).