public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kewen.Lin" <linkw@linux.ibm.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
	Mike Stump <mikestump@comcast.net>,
	David Edelsohn <dje.gcc@gmail.com>,
	Segher Boessenkool <segher@kernel.crashing.org>,
	Kewen Lin <linkw@gcc.gnu.org>,
	gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] [testsuite] [ppc] expect vectorization in gen-vect-11c.c
Date: Mon, 27 Mar 2023 15:03:39 +0800	[thread overview]
Message-ID: <2628ca10-9e16-51fc-91a0-8ff548657cc6@linux.ibm.com> (raw)
In-Reply-To: <orlejlgrdf.fsf@lxoliva.fsfla.org>

Hi Alexandre,

on 2023/3/25 16:35, Alexandre Oliva wrote:
> 
> The first loop in main gets stores "vectorized" on powerpc into
> full-word stores, even without any vector instruction support, so the
> test's expectation of no loop vectorization is not met.
> 

I think this test issue has been gone since r13-5771-gdc87e1391c55c6.

Could you have a double check?

BR,
Kewen

> Regstrapped on ppc64-linux-gnu.  Also tested with ppc64-vxworks7r2
> (gcc-12).  Ok to install?
> 
> 
> for  gcc/testsuite/ChangeLog
> 
> 	* gcc.dg/tree-ssa/gen-vect-11c.c: xfail the test for no
> 	vectorization on powerpc*-*-*.
> ---
>  gcc/testsuite/gcc.dg/tree-ssa/gen-vect-11c.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/gcc/testsuite/gcc.dg/tree-ssa/gen-vect-11c.c b/gcc/testsuite/gcc.dg/tree-ssa/gen-vect-11c.c
> index 22ff44cf66da9..116f6af233887 100644
> --- a/gcc/testsuite/gcc.dg/tree-ssa/gen-vect-11c.c
> +++ b/gcc/testsuite/gcc.dg/tree-ssa/gen-vect-11c.c
> @@ -39,4 +39,4 @@ int main ()
>  }
> 
> 
> -/* { dg-final { scan-tree-dump-times "vectorized 0 loops" 1 "vect" { xfail amdgcn*-*-* } } } */
> +/* { dg-final { scan-tree-dump-times "vectorized 0 loops" 1 "vect" { xfail amdgcn*-*-* powerpc*-*-* } } } */
> 

  reply	other threads:[~2023-03-27  7:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-25  8:35 Alexandre Oliva
2023-03-27  7:03 ` Kewen.Lin [this message]
2023-04-06  5:20   ` Alexandre Oliva
2023-04-06  6:48     ` Kewen.Lin
2023-04-07  4:37       ` Alexandre Oliva
2023-04-07  9:57         ` Kewen.Lin

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=2628ca10-9e16-51fc-91a0-8ff548657cc6@linux.ibm.com \
    --to=linkw@linux.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=linkw@gcc.gnu.org \
    --cc=mikestump@comcast.net \
    --cc=oliva@adacore.com \
    --cc=ro@CeBiTec.Uni-Bielefeld.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).