[Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b

public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed

From: "juzhe.zhong at rivai dot ai" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
Date: Mon, 20 Nov 2023 10:11:34 +0000	[thread overview]
Message-ID: <bug-112583-4-SwgGqDM7uZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112583-4@http.gcc.gnu.org/bugzilla/>

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

JuzheZhong <juzhe.zhong at rivai dot ai> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juzhe.zhong at rivai dot ai

--- Comment #2 from JuzheZhong <juzhe.zhong at rivai dot ai> ---
I think it is redundant PR.

rv64gcv_zvl128b must be same as rv64gcv.

I saw so many FAILs as follows:

FAIL: gcc.target/riscv/rvv/autovec/binop/copysign-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/copysign-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/copysign-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/copysign-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/copysign-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/copysign-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/copysign-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/copysign-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/copysign-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/copysign-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-scalar-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-scalar-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-scalar-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-scalar-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-scalar-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-scalar-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-scalar-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-scalar-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-scalar-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vadd-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vadd-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vadd-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vadd-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vadd-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vadd-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vadd-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vadd-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vadd-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vadd-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vand-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vand-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vand-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vand-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vand-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vand-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vand-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vand-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vand-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vand-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vdiv-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vdiv-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vdiv-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vdiv-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vdiv-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vdiv-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vdiv-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vdiv-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vdiv-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vdiv-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vmax-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vmax-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vmax-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vmax-run.c execution test
FAIL: gcc.target/riscv/rvv/autovec/binop/vmax-run.c execution test


Confirm I don't have them with zvl128b. So it must be your environment issue.

I am gonna ignore this PR and go to zvl256b PR directly.

next prev parent reply	other threads:[~2023-11-20 10:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17  8:08 [Bug target/112583] New: " patrick at rivosinc dot com
2023-11-17 21:21 ` [Bug target/112583] " patrick at rivosinc dot com
2023-11-20 10:11 ` juzhe.zhong at rivai dot ai [this message]
2023-11-20 16:08 ` rdapp at gcc dot gnu.org
2023-11-20 18:04 ` patrick at rivosinc dot com
2023-11-20 23:45 ` patrick at rivosinc dot com
2023-11-21 17:25 ` patrick at rivosinc dot com
2023-11-27 17:25 ` patrick at rivosinc dot com
2023-11-27 17:34 ` pinskia at gcc dot gnu.org
2023-12-04  4:01 ` juzhe.zhong at rivai dot ai
2023-12-04 10:23 ` rdapp at gcc dot gnu.org
2023-12-04 12:53 ` rdapp at gcc dot gnu.org
2023-12-04 13:09 ` rdapp at gcc dot gnu.org
2023-12-04 21:21 ` patrick at rivosinc dot com
2023-12-05  7:42 ` rdapp at gcc dot gnu.org
2023-12-11 19:57 ` 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-112583-4-SwgGqDM7uZ@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).