public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Law <law@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/vendors/riscv/heads/gcc-13-with-riscv-opts)] test: Block vect_strided5 for slp-34-big-array.c SLP check
Date: Mon, 18 Sep 2023 18:27:11 +0000 (GMT)	[thread overview]
Message-ID: <20230918182711.2A3E3385770D@sourceware.org> (raw)

https://gcc.gnu.org/g:2d7a9f4cf3a17c396de792c9b82d3f04bf8d6af4

commit 2d7a9f4cf3a17c396de792c9b82d3f04bf8d6af4
Author: Juzhe-Zhong <juzhe.zhong@rivai.ai>
Date:   Fri Sep 15 17:54:44 2023 +0800

    test: Block vect_strided5 for slp-34-big-array.c SLP check
    
    If failed on RISC-V since it use vect_store_lanes with array 5.
    
    gcc/testsuite/ChangeLog:
    
            * gcc.dg/vect/slp-34-big-array.c: Block SLP check for vect_strided5.
    
    (cherry picked from commit 16c5d0f0c4c6f72bdfc01c640f11a845530c4d3d)

Diff:
---
 gcc/testsuite/gcc.dg/vect/slp-34-big-array.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/vect/slp-34-big-array.c b/gcc/testsuite/gcc.dg/vect/slp-34-big-array.c
index 9e9c8207f7b..8345b12bb0c 100644
--- a/gcc/testsuite/gcc.dg/vect/slp-34-big-array.c
+++ b/gcc/testsuite/gcc.dg/vect/slp-34-big-array.c
@@ -62,5 +62,5 @@ int main (void)
 }
 
 /* { dg-final { scan-tree-dump-times "vectorized 1 loops" 1 "vect" } } */
-/* { dg-final { scan-tree-dump-times "vectorizing stmts using SLP" 2 "vect"  } } */
+/* { dg-final { scan-tree-dump-times "vectorizing stmts using SLP" 2 "vect" { target {! vect_strided5 } } } } */

                 reply	other threads:[~2023-09-18 18:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230918182711.2A3E3385770D@sourceware.org \
    --to=law@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).