Bug 112583 - RISC-V regression testsuite errors with rv64gcv_zvl128b
Summary: RISC-V regression testsuite errors with rv64gcv_zvl128b
Status: RESOLVED FIXED
Alias: None
Product: gcc
Classification: Unclassified
Component: target (show other bugs)
Version: 14.0
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords: testsuite-fail
Depends on:
Blocks:
 
Reported: 2023-11-17 08:08 UTC by Patrick O'Neill
Modified: 2024-01-24 23:53 UTC (History)
2 users (show)

See Also:
Host:
Target: riscv
Build:
Known to work:
Known to fail:
Last reconfirmed:

Attachments
rv64gcv_zvl128b testsuite failures (2.93 KB, text/plain)
2023-11-17 08:08 UTC, Patrick O'Neill 		Details
rv64gcv_zvl128b testsuite failures 2023-11-21 (1.82 KB, text/plain)
2023-11-21 17:25 UTC, Patrick O'Neill 		Details
rv64gcv_zvl128b testsuite failures 2023-11-27 (1.68 KB, text/plain)
2023-11-27 17:25 UTC, Patrick O'Neill 		Details
rv32gcv_zvl128b testsuite failures 2023-12-03 (1.58 KB, text/plain)
2023-12-04 21:21 UTC, Patrick O'Neill 		Details
rv64gcv_zvl128b testsuite failures 2023-12-10 (1.90 KB, text/plain)
2023-12-11 19:57 UTC, Patrick O'Neill 		Details
Show Obsolete (4) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick O'Neill 2023-11-17 08:08:10 UTC 
Created attachment 56615 [details]
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
Comment 2 JuzheZhong 2023-11-20 10:11:34 UTC 
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.
Comment 3 Robin Dapp 2023-11-20 16:08:58 UTC 
I cannot reproduce this either.  Just started with binop/* and don't see any fails locally.  Patrick, could you check what caused this?
Comment 4 Patrick O'Neill 2023-11-20 18:04:13 UTC 
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.
Comment 5 Patrick O'Neill 2023-11-20 23:45:25 UTC 
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!
Comment 6 Patrick O'Neill 2023-11-21 17:25:05 UTC 
Created attachment 56659 [details]
rv64gcv_zvl128b testsuite failures 2023-11-21

Failures here now match the failures with the default rv64gcv configuration.
Tested with hash 30d8188e6d1b450533ab0055b951ebfc75022219
Comment 7 Patrick O'Neill 2023-11-27 17:25:38 UTC 
Created attachment 56698 [details]
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
Comment 8 Andrew Pinski 2023-11-27 17:34:36 UTC 
(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.
Comment 9 JuzheZhong 2023-12-04 04:01:23 UTC 
                === 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 ?
Comment 10 Robin Dapp 2023-12-04 10:23:11 UTC 
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.
Comment 11 Robin Dapp 2023-12-04 12:53:48 UTC 
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?
Comment 12 Robin Dapp 2023-12-04 13:09:36 UTC 
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.
Comment 13 Patrick O'Neill 2023-12-04 21:21:28 UTC 
Created attachment 56792 [details]
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
Comment 14 Robin Dapp 2023-12-05 07:42:59 UTC 
Yes, that's the culprit.  I already pushed a fix yesterday.
Comment 15 Patrick O'Neill 2023-12-11 19:57:55 UTC 
Created attachment 56851 [details]
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.
Comment 16 Patrick O'Neill 2024-01-24 23:53:38 UTC 
Closing my old tracking issues.