public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "patrick at rivosinc dot com" <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, 11 Dec 2023 19:57:55 +0000 [thread overview]
Message-ID: <bug-112583-4-CWUhSMAS0p@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
Patrick O'Neill <patrick at rivosinc dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #56792|0 |1
is obsolete| |
--- Comment #15 from Patrick O'Neill <patrick at rivosinc dot com> ---
Created attachment 56851
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56851&action=edit
rv64gcv_zvl128b testsuite failures 2023-12-10
Tested with hash fbfe43daec6443978df65530dc5f7f3f8a4e6f9e
CI run:
https://github.com/patrick-rivos/gcc-postcommit-ci/actions/runs/7158896306
Resolved failures (improved from 806789e6daa39ab0503d91c71b3faeb5d5cdd317)
FAIL: gfortran.dg/vect/pr83232.f90 -O scan-tree-dump-times slp1
"vectorizing stmts using SLP" 3
XPASS: gcc.dg/tree-ssa/ssa-fre-3.c scan-tree-dump fre1 "Replaced \\(int\\)
aa_.*with a_"
FAIL: gcc.target/riscv/rvv/autovec/pr112552.c -O3 -ftree-vectorize (test for
excess errors)
New failures (regression from 806789e6daa39ab0503d91c71b3faeb5d5cdd317)
FAIL: gcc.c-torture/unsorted/dump-noaddr.c.*r.avlprop, -O3 -g comparison
FAIL: gcc.c-torture/unsorted/dump-noaddr.c.*r.reload, -O3 -g comparison
FAIL: gcc.dg/debug/btf/btf-datasec-3.c scan-assembler-times bts_type 3
FAIL: gcc.dg/debug/btf/btf-datasec-3.c scan-assembler-times bts_type:
\\(BTF_KIND_VAR 'test_bss2'\\) 1
FAIL: gcc.dg/debug/btf/btf-datasec-3.c scan-assembler-times bts_type:
\\(BTF_KIND_VAR 'test_data2'\\) 1
FAIL: gcc.dg/Wstringop-overflow-47.c pr97027 (test for warnings, line 72)
FAIL: gcc.dg/Wstringop-overflow-47.c pr97027 (test for warnings, line 77)
FAIL: gcc.dg/Wstringop-overflow-47.c pr97027 note (test for warnings, line 68)
XPASS: gcc.dg/vect/bb-slp-68.c -flto -ffat-lto-objects scan-tree-dump-not slp2
"from scalars"
XPASS: gcc.dg/vect/bb-slp-68.c scan-tree-dump-not slp2 "from scalars"
FAIL: gcc.dg/vect/bb-slp-cond-1.c -flto -ffat-lto-objects scan-tree-dump-times
vect "loop vectorized" 2
FAIL: gcc.dg/vect/bb-slp-cond-1.c scan-tree-dump-times vect "loop vectorized" 2
FAIL: gcc.dg/vect/bb-slp-pr65935.c -flto -ffat-lto-objects
scan-tree-dump-times slp1 "optimized: basic block" 11
FAIL: gcc.dg/vect/bb-slp-pr65935.c scan-tree-dump-times slp1 "optimized: basic
block" 11
FAIL: gcc.dg/vect/bb-slp-subgroups-2.c -flto -ffat-lto-objects
scan-tree-dump-times slp2 "optimized: basic block" 1
FAIL: gcc.dg/vect/bb-slp-subgroups-2.c scan-tree-dump-times slp2 "optimized:
basic block" 1
XPASS: gcc.dg/vect/bb-slp-subgroups-3.c -flto -ffat-lto-objects
scan-tree-dump-times slp2 "optimized: basic block" 2
XPASS: gcc.dg/vect/bb-slp-subgroups-3.c scan-tree-dump-times slp2 "optimized:
basic block" 2
FAIL: gcc.dg/vect/pr66251.c -flto -ffat-lto-objects scan-tree-dump-times vect
"vectorized 1 loops" 2
FAIL: gcc.dg/vect/pr66251.c scan-tree-dump-times vect "vectorized 1 loops" 2
FAIL: gcc.dg/vect/slp-reduc-sad-2.c -flto -ffat-lto-objects scan-tree-dump-not
vect "access with gaps requires scalar epilogue loop"
FAIL: gcc.dg/vect/slp-reduc-sad-2.c scan-tree-dump-not vect "access with gaps
requires scalar epilogue loop"
FAIL: gcc.target/riscv/rvv/autovec/pr111751.c -O3 -ftree-vectorize
scan-assembler-not vset
FAIL: gcc.target/riscv/rvv/autovec/pr111751.c -O3 -ftree-vectorize
scan-assembler-times li\\s+[a-x0-9]+,0\\s+ret 2
FAIL: gcc.target/riscv/rvv/base/cpymem-1.c check-function-bodies f3
FAIL: gcc.target/riscv/rvv/base/cpymem-2.c check-function-bodies f2
FAIL: gcc.target/riscv/rvv/base/cpymem-2.c check-function-bodies f3
None of these new failures are ICEs, execution, or excess errors.
FAIL: gcc.c-torture/unsorted/dump-noaddr.c.*r.avlprop, -O3 -g comparison
FAIL: gcc.c-torture/unsorted/dump-noaddr.c.*r.reload, -O3 -g comparison
These are flaky failures that Edwin is looking at/bisecting now.
next prev parent reply other threads:[~2023-12-11 19:57 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
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 [this message]
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-CWUhSMAS0p@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).