public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112598] RISC-V regression testsuite errors with rv64gcv_zvl512b
Date: Wed, 22 Nov 2023 12:31:09 +0000	[thread overview]
Message-ID: <bug-112598-4-vb8wNkNL1Q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112598-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112598

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Pan Li <panli@gcc.gnu.org>:

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

commit r14-5755-gde6f3e12bd188fee30bc79a5e323e16e0dbbe8ca
Author: Juzhe-Zhong <juzhe.zhong@rivai.ai>
Date:   Wed Nov 22 18:53:22 2023 +0800

    RISC-V: Fix incorrect use of vcompress in permutation auto-vectorization

    This patch fixes following FAILs on zvl512b of RV32 system:

    FAIL: gcc.target/riscv/rvv/autovec/struct/struct_vect_run-12.c execution
test
    FAIL: gcc.target/riscv/rvv/autovec/struct/struct_vect_run-9.c execution
test

    The root cause is that for permutation indice = {0,3,7,0} use vcompress
optimization
    which is incorrect. Fix vcompress optimization bug.

            PR target/112598

    gcc/ChangeLog:

            * config/riscv/riscv-v.cc (shuffle_compress_patterns): Fix
vcompress bug.

    gcc/testsuite/ChangeLog:

            * gcc.target/riscv/rvv/autovec/pr112598-3.c: New test.

  parent reply	other threads:[~2023-11-22 12:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 21:18 [Bug target/112598] New: " patrick at rivosinc dot com
2023-11-17 21:21 ` [Bug target/112598] " patrick at rivosinc dot com
2023-11-21  2:43 ` juzhe.zhong at rivai dot ai
2023-11-21 13:38 ` cvs-commit at gcc dot gnu.org
2023-11-21 17:43 ` patrick at rivosinc dot com
2023-11-22  6:45 ` cvs-commit at gcc dot gnu.org
2023-11-22 11:09 ` juzhe.zhong at rivai dot ai
2023-11-22 12:31 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-23  6:02 ` pan2.li at intel dot com
2023-11-24  2:37 ` pan2.li at intel dot com
2023-11-27  3:07 ` pan2.li at intel dot com
2023-11-27  8:15 ` rdapp at gcc dot gnu.org
2023-11-27  8:25 ` pan2.li at intel dot com
2023-11-27  8:43 ` rdapp at gcc dot gnu.org
2023-11-27 11:37 ` pan2.li at intel dot com
2023-11-27 12:42 ` rdapp at gcc dot gnu.org
2023-11-27 17:51 ` patrick at rivosinc dot com
2023-11-28  3:15 ` pan2.li at intel dot com
2023-12-04 21:35 ` patrick at rivosinc dot com
2023-12-11 23:48 ` patrick at rivosinc dot com
2024-01-24 23:53 ` patrick at rivosinc dot com

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=bug-112598-4-vb8wNkNL1Q@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).