From: "Kewen.Lin" <linkw@linux.ibm.com>
To: Jiufu Guo <guojiufu@linux.ibm.com>
Cc: segher@kernel.crashing.org, dje.gcc@gmail.com, linkw@gcc.gnu.org,
rguenther@suse.de, jeffreyalaw@gmail.com,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] PR testsuite/106879 FAIL: gcc.dg/vect/bb-slp-layout-19.c on powerpc64
Date: Wed, 19 Apr 2023 10:53:45 +0800 [thread overview]
Message-ID: <4c9eba2a-28ec-a463-ab0b-5daab8d382d7@linux.ibm.com> (raw)
In-Reply-To: <20230419020336.722450-1-guojiufu@linux.ibm.com>
Hi Jeff,
on 2023/4/19 10:03, Jiufu Guo wrote:
> Hi,
>
> On P7, option -mno-allow-movmisalign is added during testing, which
> prevents slp happen on the case.
>
> Like Like PR65484 and PR87306, this patch use vect_hw_misalig to guard
Dup like... ~~ missing the last character n.
> the case on powerpc targets.
>
> Tested on ppc64{le,} and x86_64.
> Is this ok for trunk?
>
> BR,
> Jeff (Jiufu)
>
> gcc/testsuite/ChangeLog:
>
> PR testsuite/106879
> * gcc.dg/vect/bb-slp-layout-19.c: Modify to guard the check with
> vect_hw_misalig on POWERs.
... ~~~~~ Same here.
OK for trunk with these nits fixed, thanks!
BR,
Kewen
>
> ---
> gcc/testsuite/gcc.dg/vect/bb-slp-layout-19.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/gcc/testsuite/gcc.dg/vect/bb-slp-layout-19.c b/gcc/testsuite/gcc.dg/vect/bb-slp-layout-19.c
> index f075a83a25b..faf98e8d3c0 100644
> --- a/gcc/testsuite/gcc.dg/vect/bb-slp-layout-19.c
> +++ b/gcc/testsuite/gcc.dg/vect/bb-slp-layout-19.c
> @@ -31,4 +31,9 @@ void f()
> e[3] = b3;
> }
>
> -/* { dg-final { scan-tree-dump-times "add new stmt: \[^\\n\\r\]* = VEC_PERM_EXPR" 3 "slp1" { target { vect_int_mult && vect_perm } } } } */
> +/* On older powerpc hardware (POWER7 and earlier), the default flag
> + -mno-allow-movmisalign prevents vectorization. On POWER8 and later,
> + when vect_hw_misalign is true, vectorization occurs. For other
> + targets, ! vect_no_align is a sufficient test. */
> +
> +/* { dg-final { scan-tree-dump-times "add new stmt: \[^\\n\\r\]* = VEC_PERM_EXPR" 3 "slp1" { target { { vect_int_mult && vect_perm } && { { ! powerpc*-*-* } || { vect_hw_misalign } } } } } } */
next prev parent reply other threads:[~2023-04-19 2:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 2:03 Jiufu Guo
2023-04-19 2:53 ` Kewen.Lin [this message]
2023-04-20 4:37 ` guojiufu
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=4c9eba2a-28ec-a463-ab0b-5daab8d382d7@linux.ibm.com \
--to=linkw@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=guojiufu@linux.ibm.com \
--cc=jeffreyalaw@gmail.com \
--cc=linkw@gcc.gnu.org \
--cc=rguenther@suse.de \
--cc=segher@kernel.crashing.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).