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)] RISC-V Regression: Fix FAIL of bb-slp-68.c for RVV
Date: Mon, 16 Oct 2023 18:38:56 +0000 (GMT)	[thread overview]
Message-ID: <20231016183856.1884C385C6F5@sourceware.org> (raw)

https://gcc.gnu.org/g:4b0f502e0df34b23aef259d320ef220bca1a819a

commit 4b0f502e0df34b23aef259d320ef220bca1a819a
Author: Juzhe-Zhong <juzhe.zhong@rivai.ai>
Date:   Fri Oct 13 14:01:26 2023 +0800

    RISC-V Regression: Fix FAIL of bb-slp-68.c for RVV
    
    Like comment said, this test failed on 64 bytes vector.
    Both RVV and GCN has 64 bytes vector.
    
    So it's more reasonable to use vect512.
    gcc/testsuite/ChangeLog:
    
            * gcc.dg/vect/bb-slp-68.c: Use vect512.
    
    (cherry picked from commit 8544efd6d4aea46656c37b0e002503616f09edfc)

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

diff --git a/gcc/testsuite/gcc.dg/vect/bb-slp-68.c b/gcc/testsuite/gcc.dg/vect/bb-slp-68.c
index e7573a14933e..2dd3d8ee90c6 100644
--- a/gcc/testsuite/gcc.dg/vect/bb-slp-68.c
+++ b/gcc/testsuite/gcc.dg/vect/bb-slp-68.c
@@ -20,4 +20,4 @@ void foo ()
 
 /* We want to have the store group split into 4, 2, 4 when using 32byte vectors.
    Unfortunately it does not work when 64-byte vectors are available.  */
-/* { dg-final { scan-tree-dump-not "from scalars" "slp2" { xfail amdgcn-*-* } } } */
+/* { dg-final { scan-tree-dump-not "from scalars" "slp2" { xfail vect512 } } } */

                 reply	other threads:[~2023-10-16 18:38 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=20231016183856.1884C385C6F5@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).