public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b
@ 2023-11-17 8:08 patrick at rivosinc dot com
2023-11-17 21:21 ` [Bug target/112583] " patrick at rivosinc dot com
` (15 more replies)
0 siblings, 16 replies; 17+ messages in thread
From: patrick at rivosinc dot com @ 2023-11-17 8:08 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
Bug ID: 112583
Summary: RISC-V regression testsuite errors with
rv64gcv_zvl128b
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: patrick at rivosinc dot com
Target Milestone: ---
Created attachment 56615
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56615&action=edit
rv64gcv_zvl128b testsuite failures
Current testsuite status of rv64gcv_zvl128b on GCC
5cb13173e85537a8a423b7b22b60ca3b6505f91e
I've started running zvl variants 128-1024b weekly on the postcommit CI. This
is my first time running these so if any of the failures look odd poke me here
or via email and I can dig into/share the logs.
Artifacts for this run can be downloaded here:
https://github.com/patrick-rivos/gcc-postcommit-ci/actions/runs/6898356494
Likely artifacts of interest:
gcc-linux-rv64gcv_zvl-lp64d-5cb13173e85537a8a423b7b22b60ca3b6505f91e-multilib-debug-output.log
gcc-linux-rv64gcv_zvl-lp64d-5cb13173e85537a8a423b7b22b60ca3b6505f91e-multilib-report.log
gcc-linux-rv64gcv_zvl-lp64d-5cb13173e85537a8a423b7b22b60ca3b6505f91e-multilib-sum-files
This is just a tracking issue, similar to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111311
I'll open separate tracking issues for zvl 256,512,1024 tomorrow.
I've attached the current results for rv64gcv_zvl128b with glibc v2.37 on QEMU
v8.1.2
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b patrick at rivosinc dot com
@ 2023-11-17 21:21 ` patrick at rivosinc dot com
2023-11-20 10:11 ` juzhe.zhong at rivai dot ai
` (14 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: patrick at rivosinc dot com @ 2023-11-17 21:21 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #1 from Patrick O'Neill <patrick at rivosinc dot com> ---
Related issues:
128: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
256: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112597
512: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112598
1024: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112599
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b 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
` (13 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: juzhe.zhong at rivai dot ai @ 2023-11-20 10:11 UTC (permalink / raw)
To: gcc-bugs
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.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b 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
` (12 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: rdapp at gcc dot gnu.org @ 2023-11-20 16:08 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #3 from Robin Dapp <rdapp at gcc dot gnu.org> ---
I cannot reproduce this either. Just started with binop/* and don't see any
fails locally. Patrick, could you check what caused this?
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b patrick at rivosinc dot com
` (2 preceding siblings ...)
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
` (11 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: patrick at rivosinc dot com @ 2023-11-20 18:04 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #4 from Patrick O'Neill <patrick at rivosinc dot com> ---
Investigating this now. I'll let you know what I find out.
All these tests were run in the same environment so be wary when looking at any
of them until I figure out the environment issue.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b patrick at rivosinc dot com
` (3 preceding siblings ...)
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
` (10 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: patrick at rivosinc dot com @ 2023-11-20 23:45 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #5 from Patrick O'Neill <patrick at rivosinc dot com> ---
I built all the zvl variants as a multilib. It seems like that caused them to
interfere with eachother (potentially picking up the wrong glibc?). I'll rerun
with separate runs & update the issues with updated logs once it's done.
Thanks for catching this!
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b patrick at rivosinc dot com
` (4 preceding siblings ...)
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
` (9 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: patrick at rivosinc dot com @ 2023-11-21 17:25 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
Patrick O'Neill <patrick at rivosinc dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #56615|0 |1
is obsolete| |
--- Comment #6 from Patrick O'Neill <patrick at rivosinc dot com> ---
Created attachment 56659
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56659&action=edit
rv64gcv_zvl128b testsuite failures 2023-11-21
Failures here now match the failures with the default rv64gcv configuration.
Tested with hash 30d8188e6d1b450533ab0055b951ebfc75022219
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b patrick at rivosinc dot com
` (5 preceding siblings ...)
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
` (8 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: patrick at rivosinc dot com @ 2023-11-27 17:25 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
Patrick O'Neill <patrick at rivosinc dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #56659|0 |1
is obsolete| |
--- Comment #7 from Patrick O'Neill <patrick at rivosinc dot com> ---
Created attachment 56698
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56698&action=edit
rv64gcv_zvl128b testsuite failures 2023-11-27
Tested with hash 9866c98e1015d98b8fc346d7cf73a0070cce5f69
CI run:
https://github.com/patrick-rivos/gcc-postcommit-ci/actions/runs/6988591247
Resolved failures (improved from 30d8188e6d1b450533ab0055b951ebfc75022219)
ERROR: gcc.dg/tree-ssa/return-value-range-1.c: 1: syntax error for " dg-do 1
ling "
ERROR: gcc.dg/tree-ssa/return-value-range-1.c: 1: syntax error for " dg-do 1
ling "
FAIL: gcc.dg/tree-ssa/ssa-lim-11.c scan-tree-dump-times lim2 "Executing store
motion of __gcov0.access_buf\\[[12]\\] from loop 1" 2
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_run-12.c
execution test
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_run-12.c
execution test
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_run-12.c
execution test
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_run-12.c
execution test
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_run-12.c
execution test
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_run-12.c
execution test
FAIL: gcc.dg/gomp/pr27573.c (internal compiler error: verify_gimple failed)
FAIL: gcc.dg/gomp/pr27573.c (test for excess errors)
FAIL: gfortran.dg/gomp/pr27573.f90 -O (internal compiler error:
verify_gimple failed)
FAIL: gfortran.dg/gomp/pr27573.f90 -O (test for excess errors)
FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++2b (test for excess errors)
New failures (regression from 30d8188e6d1b450533ab0055b951ebfc75022219)
FAIL: gcc.dg/tree-prof/time-profiler-3.c scan-ipa-dump-times profile "Read
tp_first_run: 0" 1
FAIL: gcc.dg/tree-prof/time-profiler-3.c scan-ipa-dump-times profile "Read
tp_first_run: 2" 1
These new fails were introduced in this range of commits:
https://github.com/gcc-mirror/gcc/compare/7bf1de918608e2d0b5a3ad0923040acb1819d9a5...41aacdea55c5d795a7aa195357d966645845d00e
Postcommit CI run:
https://github.com/patrick-rivos/gcc-postcommit-ci/issues/200
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b patrick at rivosinc dot com
` (6 preceding siblings ...)
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
` (7 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-11-27 17:34 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=112689
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Patrick O'Neill from comment #7)
> New failures (regression from 30d8188e6d1b450533ab0055b951ebfc75022219)
> FAIL: gcc.dg/tree-prof/time-profiler-3.c scan-ipa-dump-times profile "Read
> tp_first_run: 0" 1
> FAIL: gcc.dg/tree-prof/time-profiler-3.c scan-ipa-dump-times profile "Read
> tp_first_run: 2" 1
Recorded as PR 112689 for aarch64 but also happens on x86_64 so I assume it is
the same issue.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b patrick at rivosinc dot com
` (7 preceding siblings ...)
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
` (6 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: juzhe.zhong at rivai dot ai @ 2023-12-04 4:01 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #9 from JuzheZhong <juzhe.zhong at rivai dot ai> ---
=== gfortran: Unexpected fails for rv64gcv lp64d medany ===
FAIL: gfortran.dg/dollar_edit_descriptor_3.f -O0 output pattern test
FAIL: gfortran.dg/dollar_edit_descriptor_3.f -O1 output pattern test
FAIL: gfortran.dg/dollar_edit_descriptor_3.f -O2 output pattern test
FAIL: gfortran.dg/dollar_edit_descriptor_3.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/dollar_edit_descriptor_3.f -O3 -g output pattern test
FAIL: gfortran.dg/dollar_edit_descriptor_3.f -Os output pattern test
FAIL: gfortran.dg/namelist_print_1.f -O0 output pattern test
FAIL: gfortran.dg/namelist_print_1.f -O1 output pattern test
FAIL: gfortran.dg/namelist_print_1.f -O2 output pattern test
FAIL: gfortran.dg/namelist_print_1.f -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/namelist_print_1.f -O3 -g output pattern test
FAIL: gfortran.dg/namelist_print_1.f -Os output pattern test
FAIL: gfortran.dg/read_x_eor.f90 -O0 output pattern test
FAIL: gfortran.dg/read_x_eor.f90 -O1 output pattern test
FAIL: gfortran.dg/read_x_eor.f90 -O2 output pattern test
FAIL: gfortran.dg/read_x_eor.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/read_x_eor.f90 -O3 -g output pattern test
FAIL: gfortran.dg/read_x_eor.f90 -Os output pattern test
FAIL: gfortran.dg/g77/f77-edit-apostrophe-out.f -O0 output pattern test
FAIL: gfortran.dg/g77/f77-edit-apostrophe-out.f -O1 output pattern test
FAIL: gfortran.dg/g77/f77-edit-apostrophe-out.f -O2 output pattern test
FAIL: gfortran.dg/g77/f77-edit-apostrophe-out.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/g77/f77-edit-apostrophe-out.f -O3 -g output pattern test
FAIL: gfortran.dg/g77/f77-edit-apostrophe-out.f -Os output pattern test
FAIL: gfortran.dg/g77/f77-edit-colon-out.f -O0 output pattern test
FAIL: gfortran.dg/g77/f77-edit-colon-out.f -O1 output pattern test
FAIL: gfortran.dg/g77/f77-edit-colon-out.f -O2 output pattern test
FAIL: gfortran.dg/g77/f77-edit-colon-out.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/g77/f77-edit-colon-out.f -O3 -g output pattern test
FAIL: gfortran.dg/g77/f77-edit-colon-out.f -Os output pattern test
FAIL: gfortran.dg/g77/f77-edit-h-out.f -O0 output pattern test
FAIL: gfortran.dg/g77/f77-edit-h-out.f -O1 output pattern test
FAIL: gfortran.dg/g77/f77-edit-h-out.f -O2 output pattern test
FAIL: gfortran.dg/g77/f77-edit-h-out.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/g77/f77-edit-h-out.f -O3 -g output pattern test
FAIL: gfortran.dg/g77/f77-edit-h-out.f -Os output pattern test
FAIL: gfortran.dg/g77/f77-edit-i-out.f -O0 output pattern test
FAIL: gfortran.dg/g77/f77-edit-i-out.f -O1 output pattern test
FAIL: gfortran.dg/g77/f77-edit-i-out.f -O2 output pattern test
FAIL: gfortran.dg/g77/f77-edit-i-out.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/g77/f77-edit-i-out.f -O3 -g output pattern test
FAIL: gfortran.dg/g77/f77-edit-i-out.f -Os output pattern test
FAIL: gfortran.dg/g77/f77-edit-s-out.f -O0 output pattern test
FAIL: gfortran.dg/g77/f77-edit-s-out.f -O1 output pattern test
FAIL: gfortran.dg/g77/f77-edit-s-out.f -O2 output pattern test
FAIL: gfortran.dg/g77/f77-edit-s-out.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/g77/f77-edit-s-out.f -O3 -g output pattern test
FAIL: gfortran.dg/g77/f77-edit-s-out.f -Os output pattern test
FAIL: gfortran.dg/g77/f77-edit-slash-out.f -O0 output pattern test
FAIL: gfortran.dg/g77/f77-edit-slash-out.f -O1 output pattern test
FAIL: gfortran.dg/g77/f77-edit-slash-out.f -O2 output pattern test
FAIL: gfortran.dg/g77/f77-edit-slash-out.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/g77/f77-edit-slash-out.f -O3 -g output pattern test
FAIL: gfortran.dg/g77/f77-edit-slash-out.f -Os output pattern test
FAIL: gfortran.dg/g77/f77-edit-t-out.f -O0 output pattern test
FAIL: gfortran.dg/g77/f77-edit-t-out.f -O1 output pattern test
FAIL: gfortran.dg/g77/f77-edit-t-out.f -O2 output pattern test
FAIL: gfortran.dg/g77/f77-edit-t-out.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/g77/f77-edit-t-out.f -O3 -g output pattern test
FAIL: gfortran.dg/g77/f77-edit-t-out.f -Os output pattern test
FAIL: gfortran.dg/g77/f77-edit-x-out.f -O0 output pattern test
FAIL: gfortran.dg/g77/f77-edit-x-out.f -O1 output pattern test
FAIL: gfortran.dg/g77/f77-edit-x-out.f -O2 output pattern test
FAIL: gfortran.dg/g77/f77-edit-x-out.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/g77/f77-edit-x-out.f -O3 -g output pattern test
FAIL: gfortran.dg/g77/f77-edit-x-out.f -Os output pattern test
FAIL: gfortran.dg/vect/pr83232.f90 -O scan-tree-dump-times slp1
"vectorizing stmts using SLP" 3
FAIL: gfortran.dg/vect/vect-8.f90 -O scan-tree-dump-times vect "vectorized
2[234] loops" 1
=== gfortran: Unexpected fails for rv64gcv lp64d medany
--param=riscv-autovec-lmul=m1 --param=riscv-autovec-preference=scalable ===
FAIL: gfortran.dg/dollar_edit_descriptor_3.f -O0 output pattern test
FAIL: gfortran.dg/dollar_edit_descriptor_3.f -O1 output pattern test
FAIL: gfortran.dg/dollar_edit_descriptor_3.f -O2 output pattern test
FAIL: gfortran.dg/dollar_edit_descriptor_3.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/dollar_edit_descriptor_3.f -O3 -g output pattern test
FAIL: gfortran.dg/dollar_edit_descriptor_3.f -Os output pattern test
FAIL: gfortran.dg/namelist_print_1.f -O0 output pattern test
FAIL: gfortran.dg/namelist_print_1.f -O1 output pattern test
FAIL: gfortran.dg/namelist_print_1.f -O2 output pattern test
FAIL: gfortran.dg/namelist_print_1.f -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/namelist_print_1.f -O3 -g output pattern test
FAIL: gfortran.dg/namelist_print_1.f -Os output pattern test
FAIL: gfortran.dg/read_x_eor.f90 -O0 output pattern test
FAIL: gfortran.dg/read_x_eor.f90 -O1 output pattern test
FAIL: gfortran.dg/read_x_eor.f90 -O2 output pattern test
FAIL: gfortran.dg/read_x_eor.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/read_x_eor.f90 -O3 -g output pattern test
FAIL: gfortran.dg/read_x_eor.f90 -Os output pattern test
FAIL: gfortran.dg/g77/f77-edit-apostrophe-out.f -O0 output pattern test
FAIL: gfortran.dg/g77/f77-edit-apostrophe-out.f -O1 output pattern test
FAIL: gfortran.dg/g77/f77-edit-apostrophe-out.f -O2 output pattern test
FAIL: gfortran.dg/g77/f77-edit-apostrophe-out.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/g77/f77-edit-apostrophe-out.f -O3 -g output pattern test
FAIL: gfortran.dg/g77/f77-edit-apostrophe-out.f -Os output pattern test
FAIL: gfortran.dg/g77/f77-edit-colon-out.f -O0 output pattern test
FAIL: gfortran.dg/g77/f77-edit-colon-out.f -O1 output pattern test
FAIL: gfortran.dg/g77/f77-edit-colon-out.f -O2 output pattern test
FAIL: gfortran.dg/g77/f77-edit-colon-out.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/g77/f77-edit-colon-out.f -O3 -g output pattern test
FAIL: gfortran.dg/g77/f77-edit-colon-out.f -Os output pattern test
FAIL: gfortran.dg/g77/f77-edit-h-out.f -O0 output pattern test
FAIL: gfortran.dg/g77/f77-edit-h-out.f -O1 output pattern test
FAIL: gfortran.dg/g77/f77-edit-h-out.f -O2 output pattern test
FAIL: gfortran.dg/g77/f77-edit-h-out.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/g77/f77-edit-h-out.f -O3 -g output pattern test
FAIL: gfortran.dg/g77/f77-edit-h-out.f -Os output pattern test
FAIL: gfortran.dg/g77/f77-edit-i-out.f -O0 output pattern test
FAIL: gfortran.dg/g77/f77-edit-i-out.f -O1 output pattern test
FAIL: gfortran.dg/g77/f77-edit-i-out.f -O2 output pattern test
FAIL: gfortran.dg/g77/f77-edit-i-out.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/g77/f77-edit-i-out.f -O3 -g output pattern test
FAIL: gfortran.dg/g77/f77-edit-i-out.f -Os output pattern test
FAIL: gfortran.dg/g77/f77-edit-s-out.f -O0 output pattern test
FAIL: gfortran.dg/g77/f77-edit-s-out.f -O1 output pattern test
FAIL: gfortran.dg/g77/f77-edit-s-out.f -O2 output pattern test
FAIL: gfortran.dg/g77/f77-edit-s-out.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/g77/f77-edit-s-out.f -O3 -g output pattern test
FAIL: gfortran.dg/g77/f77-edit-s-out.f -Os output pattern test
FAIL: gfortran.dg/g77/f77-edit-slash-out.f -O0 output pattern test
FAIL: gfortran.dg/g77/f77-edit-slash-out.f -O1 output pattern test
FAIL: gfortran.dg/g77/f77-edit-slash-out.f -O2 output pattern test
FAIL: gfortran.dg/g77/f77-edit-slash-out.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/g77/f77-edit-slash-out.f -O3 -g output pattern test
FAIL: gfortran.dg/g77/f77-edit-slash-out.f -Os output pattern test
FAIL: gfortran.dg/g77/f77-edit-t-out.f -O0 output pattern test
FAIL: gfortran.dg/g77/f77-edit-t-out.f -O1 output pattern test
FAIL: gfortran.dg/g77/f77-edit-t-out.f -O2 output pattern test
FAIL: gfortran.dg/g77/f77-edit-t-out.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/g77/f77-edit-t-out.f -O3 -g output pattern test
FAIL: gfortran.dg/g77/f77-edit-t-out.f -Os output pattern test
FAIL: gfortran.dg/g77/f77-edit-x-out.f -O0 output pattern test
FAIL: gfortran.dg/g77/f77-edit-x-out.f -O1 output pattern test
FAIL: gfortran.dg/g77/f77-edit-x-out.f -O2 output pattern test
FAIL: gfortran.dg/g77/f77-edit-x-out.f -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions output pattern test
FAIL: gfortran.dg/g77/f77-edit-x-out.f -O3 -g output pattern test
FAIL: gfortran.dg/g77/f77-edit-x-out.f -Os output pattern test
FAIL: gfortran.dg/vect/pr83232.f90 -O scan-tree-dump-times slp1
"vectorizing stmts using SLP" 3
FAIL: gfortran.dg/vect/vect-8.f90 -O scan-tree-dump-times vect "vectorized
2[234] loops" 1
I saw many execution FAILs in fortran.
Hi, Robin. Do you know the reasons ?
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b patrick at rivosinc dot com
` (8 preceding siblings ...)
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
` (5 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: rdapp at gcc dot gnu.org @ 2023-12-04 10:23 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #10 from Robin Dapp <rdapp at gcc dot gnu.org> ---
I didn't yet look at all those closer because they are more dump failures than
real execution failures.
The ones I checked are
expected
"^foobar$" but got:
"foobar"
so I considered this rather an environment problem than a real problem (like
qemu stripping the output or so). But who knows. Going to have a closer look
this week. On my machine those pass at least.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b patrick at rivosinc dot com
` (9 preceding siblings ...)
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
` (4 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: rdapp at gcc dot gnu.org @ 2023-12-04 12:53 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #11 from Robin Dapp <rdapp at gcc dot gnu.org> ---
Verified they work locally but also fail on a different server. Also fail
without vector and at -O0. Maybe it's different tcl versions or the shell
doing wonky stuff?
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b patrick at rivosinc dot com
` (10 preceding siblings ...)
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
` (3 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: rdapp at gcc dot gnu.org @ 2023-12-04 13:09 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #12 from Robin Dapp <rdapp at gcc dot gnu.org> ---
Ok, on my server the difference is that I didn't add vext_spec=v1.0 to the qemu
options. This caused the qemu diagnostic which would of course not match the
expected output.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b patrick at rivosinc dot com
` (11 preceding siblings ...)
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
` (2 subsequent siblings)
15 siblings, 0 replies; 17+ messages in thread
From: patrick at rivosinc dot com @ 2023-12-04 21:21 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
Patrick O'Neill <patrick at rivosinc dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #56698|0 |1
is obsolete| |
--- Comment #13 from Patrick O'Neill <patrick at rivosinc dot com> ---
Created attachment 56792
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56792&action=edit
rv32gcv_zvl128b testsuite failures 2023-12-03
Tested with hash 806789e6daa39ab0503d91c71b3faeb5d5cdd317
CI run:
https://github.com/patrick-rivos/gcc-postcommit-ci/actions/runs/7077949347
Resolved failures (improved from 9866c98e1015d98b8fc346d7cf73a0070cce5f69)
FAIL: g++.dg/contracts/contracts-tmpl-spec2.C output pattern test
XPASS: gcc.dg/uninit-pred-9_b.c bogus warning (test for bogus messages, line
20)
FAIL: gcc.dg/vla-1.c scan-tree-dump-times optimized " s=> i" 2
FAIL: gcc.dg/tree-prof/time-profiler-3.c scan-ipa-dump-times profile "Read
tp_first_run: 0" 1
FAIL: gcc.dg/tree-prof/time-profiler-3.c scan-ipa-dump-times profile "Read
tp_first_run: 2" 1
New failures (regression from 9866c98e1015d98b8fc346d7cf73a0070cce5f69)
FAIL: gcc.target/riscv/rvv/autovec/pr112552.c -O3 -ftree-vectorize (test for
excess errors)
Debug log for new failure:
Executing on host:
/github/patrick-postcommit-runner-2/_work/gcc-postcommit-ci/gcc-postcommit-ci/riscv-gnu-toolchain/build/build-gcc-linux-stage2/gcc/xgcc
-B/github/patrick-postcommit-runner-2/_work/gcc-postcommit-ci/gcc-postcommit-ci/riscv-gnu-toolchain/build/build-gcc-linux-stage2/gcc/
/github/patrick-postcommit-runner-2/_work/gcc-postcommit-ci/gcc-postcommit-ci/riscv-gnu-toolchain/gcc/gcc/testsuite/gcc.target/riscv/rvv/autovec/pr112552.c
-march=rv64gcv_zvl128b -mabi=lp64d -mcmodel=medlow
-fdiagnostics-plain-output -O3 -ftree-vectorize -O3 -march=rv64gcv -mabi=lp64d
--param=riscv-autovec-preference=fixed-vlmax -w -S -o pr112552.s (timeout
= 600)
spawn -ignore SIGHUP
/github/patrick-postcommit-runner-2/_work/gcc-postcommit-ci/gcc-postcommit-ci/riscv-gnu-toolchain/build/build-gcc-linux-stage2/gcc/xgcc
-B/github/patrick-postcommit-runner-2/_work/gcc-postcommit-ci/gcc-postcommit-ci/riscv-gnu-toolchain/build/build-gcc-linux-stage2/gcc/
/github/patrick-postcommit-runner-2/_work/gcc-postcommit-ci/gcc-postcommit-ci/riscv-gnu-toolchain/gcc/gcc/testsuite/gcc.target/riscv/rvv/autovec/pr112552.c
-march=rv64gcv_zvl128b -mabi=lp64d -mcmodel=medlow -fdiagnostics-plain-output
-O3 -ftree-vectorize -O3 -march=rv64gcv -mabi=lp64d
--param=riscv-autovec-preference=fixed-vlmax -w -S -o pr112552.s
/github/patrick-postcommit-runner-2/_work/gcc-postcommit-ci/gcc-postcommit-ci/riscv-gnu-toolchain/gcc/gcc/testsuite/gcc.target/riscv/rvv/autovec/pr112552.c:
In function 'h':
/github/patrick-postcommit-runner-2/_work/gcc-postcommit-ci/gcc-postcommit-ci/riscv-gnu-toolchain/gcc/gcc/testsuite/gcc.target/riscv/rvv/autovec/pr112552.c:11:15:
error: initialization of 'char *' from incompatible pointer type 'void (*)()'
[-Wincompatible-pointer-types]
compiler exited with status 1
FAIL: gcc.target/riscv/rvv/autovec/pr112552.c -O3 -ftree-vectorize (test for
excess errors)
Excess errors:
/github/patrick-postcommit-runner-2/_work/gcc-postcommit-ci/gcc-postcommit-ci/riscv-gnu-toolchain/gcc/gcc/testsuite/gcc.target/riscv/rvv/autovec/pr112552.c:11:15:
error: initialization of 'char *' from incompatible pointer type 'void (*)()'
[-Wincompatible-pointer-types]
This new failure just looks like fallout from:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=9715c545d33b3a32ddc1ae817ba9356ade1fb9df
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b patrick at rivosinc dot com
` (12 preceding siblings ...)
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
15 siblings, 0 replies; 17+ messages in thread
From: rdapp at gcc dot gnu.org @ 2023-12-05 7:42 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #14 from Robin Dapp <rdapp at gcc dot gnu.org> ---
Yes, that's the culprit. I already pushed a fix yesterday.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b patrick at rivosinc dot com
` (13 preceding siblings ...)
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
15 siblings, 0 replies; 17+ messages in thread
From: patrick at rivosinc dot com @ 2023-12-11 19:57 UTC (permalink / raw)
To: gcc-bugs
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.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b patrick at rivosinc dot com
` (14 preceding siblings ...)
2023-12-11 19:57 ` patrick at rivosinc dot com
@ 2024-01-24 23:53 ` patrick at rivosinc dot com
15 siblings, 0 replies; 17+ messages in thread
From: patrick at rivosinc dot com @ 2024-01-24 23:53 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
Patrick O'Neill <patrick at rivosinc dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #16 from Patrick O'Neill <patrick at rivosinc dot com> ---
Closing my old tracking issues.
^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2024-01-24 23:53 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-11-17 8:08 [Bug target/112583] New: RISC-V regression testsuite errors with rv64gcv_zvl128b 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
2024-01-24 23:53 ` patrick at rivosinc dot com
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).