public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] [testsuite] [ppc] expect vectorization in gen-vect-11c.c
Date: Thu,  6 Apr 2023 06:35:17 +0000 (GMT)	[thread overview]
Message-ID: <20230406063517.F2B9C3858434@sourceware.org> (raw)

https://gcc.gnu.org/g:fa27a62ca7c9c7f5ceff3c97dbd8fa3a98bef5fd

commit fa27a62ca7c9c7f5ceff3c97dbd8fa3a98bef5fd
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Wed Apr 5 11:27:21 2023 -0300

    [testsuite] [ppc] expect vectorization in gen-vect-11c.c
    
    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.
    
    
    for  gcc/testsuite/ChangeLog
    
            * gcc.dg/tree-ssa/gen-vect-11c.c: xfail the test for no
            vectorization on powerpc*-*-*.

Diff:
---
 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 22ff44cf66d..116f6af2338 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-04-06  6:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06  6:35 Alexandre Oliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-30 14:08 Alexandre Oliva
2023-03-25 14:53 Alexandre Oliva
2023-03-24  6:25 Alexandre Oliva

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=20230406063517.F2B9C3858434@sourceware.org \
    --to=aoliva@gcc.gnu.org \
    --cc=gcc-cvs@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).