From: Hao Liu OS <hliu@os.amperecomputing.com>
To: Richard Biener <rguenther@suse.de>
Cc: "GCC-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] testsuite: add the case to cover vectorization of A[(i+x)*stride] [PR114322]
Date: Wed, 20 Mar 2024 09:43:50 +0000 [thread overview]
Message-ID: <CYYPR01MB8309A7D868243AD4ECDA8B7BE1332@CYYPR01MB8309.prod.exchangelabs.com> (raw)
In-Reply-To: <7n6o2538-p829-p52r-so19-s196924o6r59@fhfr.qr>
> So - OK with using { target vect_int } instead.
Sure, it's much better to be target independent.
Refactored and committed in r14-9569-g4c276896
Thanks,
- Hao
________________________________________
From: Richard Biener <rguenther@suse.de>
Sent: Wednesday, March 20, 2024 16:21
To: Hao Liu OS
Cc: GCC-patches@gcc.gnu.org
Subject: Re: [PATCH] testsuite: add the case to cover vectorization of A[(i+x)*stride] [PR114322]
On Wed, 20 Mar 2024, Hao Liu OS wrote:
> Hi Richard,
>
> As mentioned in the comments of PR114322 (which has been fixed by PR114151
> r14-9540-ge0e9499a), this patch is to cover the case.
>
> Bootstrapped and regression tested on aarch64-linux-gnu, OK for trunk?
>
> gcc/testsuite/ChangeLog:
>
> PR tree-optimization/114322
> * gcc.dg/vect/pr114322.c: New testcase.
>
> diff --git a/gcc/testsuite/gcc.dg/vect/pr114322.c b/gcc/testsuite/gcc.dg/vect/pr114322.c
> new file mode 100644
> index 00000000000..7c3a4ffe260
> --- /dev/null
> +++ b/gcc/testsuite/gcc.dg/vect/pr114322.c
> @@ -0,0 +1,18 @@
> +/* PR tree-optimization/114322 */
> +/* { dg-do compile } */
> +
> +int
> +foo (short *A, int x, int stride)
> +{
> + int sum = 0;
> +
> + if (stride > 1)
> + {
> + for (int i = 0; i < 1024; ++i)
> + sum += A[(i + x) * stride];
> + }
> +
> + return sum;
> +}
> +
> +/* { dg-final { scan-tree-dump "LOOP VECTORIZED" "vect" { target aarch64*-*-* } } } */
I don't like the target selector very much - if you make 'A'
a 'int *', the strided access should be the important part,
vect_int should match the requirements - the strided access should
end up with VMAT_ELEMENTWISE at worst (possibly gather on aarch64?),
and VMAT_ELEMENTWISE doesn't need any alignment.
So - OK with using { target vect_int } instead.
Richard.
prev parent reply other threads:[~2024-03-20 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 7:55 Hao Liu OS
2024-03-20 8:21 ` Richard Biener
2024-03-20 9:43 ` Hao Liu OS [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=CYYPR01MB8309A7D868243AD4ECDA8B7BE1332@CYYPR01MB8309.prod.exchangelabs.com \
--to=hliu@os.amperecomputing.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).