public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robin Dapp <rdapp.gcc@gmail.com>
To: Juzhe-Zhong <juzhe.zhong@rivai.ai>, gcc-patches@gcc.gnu.org
Cc: rdapp.gcc@gmail.com, kito.cheng@gmail.com, kito.cheng@sifive.com,
	jeffreyalaw@gmail.com
Subject: Re: [PATCH V6] RISC-V: Enable vec_int testsuite for RVV VLA vectorization
Date: Tue, 12 Sep 2023 17:45:07 +0200	[thread overview]
Message-ID: <d422422f-6e12-1f99-88bb-337e18a99ac7@gmail.com> (raw)
In-Reply-To: <20230830120549.1628109-1-juzhe.zhong@rivai.ai>

The current status (for rv64gcv) is:

		=== gcc tests ===

Running target unix/-march=rv64gcv
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
XPASS: gcc.dg/vect/no-scevccp-outer-16.c scan-tree-dump-times vect "OUTER LOOP VECTORIZED." 1
XPASS: gcc.dg/vect/no-scevccp-outer-17.c scan-tree-dump-times vect "OUTER LOOP VECTORIZED." 1
XPASS: gcc.dg/vect/no-scevccp-outer-19.c scan-tree-dump-times vect "OUTER LOOP VECTORIZED." 1
XPASS: gcc.dg/vect/no-scevccp-outer-21.c scan-tree-dump-times vect "OUTER LOOP VECTORIZED." 1
FAIL: gcc.dg/vect/no-scevccp-outer-7.c scan-tree-dump-times vect "vect_recog_widen_mult_pattern: detected" 1
FAIL: gcc.dg/vect/no-scevccp-vect-iv-3.c scan-tree-dump-times vect "vect_recog_widen_sum_pattern: detected" 1
FAIL: gcc.dg/vect/pr57705.c -flto -ffat-lto-objects  scan-tree-dump-times vect "vectorized 1 loop" 2
FAIL: gcc.dg/vect/pr57705.c scan-tree-dump-times vect "vectorized 1 loop" 2
FAIL: gcc.dg/vect/pr65518.c -flto -ffat-lto-objects  scan-tree-dump-times vect "vectorized 0 loops in function" 2
FAIL: gcc.dg/vect/pr65518.c scan-tree-dump-times vect "vectorized 0 loops in function" 2
FAIL: gcc.dg/vect/slp-1.c -flto -ffat-lto-objects  scan-tree-dump-times vect "vectorizing stmts using SLP" 4
FAIL: gcc.dg/vect/slp-1.c scan-tree-dump-times vect "vectorizing stmts using SLP" 4
FAIL: gcc.dg/vect/slp-12a.c -flto -ffat-lto-objects  scan-tree-dump-times vect "vectorizing stmts using SLP" 1
FAIL: gcc.dg/vect/slp-12a.c scan-tree-dump-times vect "vectorizing stmts using SLP" 1
FAIL: gcc.dg/vect/slp-16.c -flto -ffat-lto-objects  scan-tree-dump-times vect "vectorizing stmts using SLP" 2
FAIL: gcc.dg/vect/slp-16.c scan-tree-dump-times vect "vectorizing stmts using SLP" 2
FAIL: gcc.dg/vect/slp-34-big-array.c -flto -ffat-lto-objects  scan-tree-dump-times vect "vectorizing stmts using SLP" 2
FAIL: gcc.dg/vect/slp-34-big-array.c scan-tree-dump-times vect "vectorizing stmts using SLP" 2
FAIL: gcc.dg/vect/slp-34.c -flto -ffat-lto-objects  scan-tree-dump-times vect "vectorizing stmts using SLP" 2
FAIL: gcc.dg/vect/slp-34.c scan-tree-dump-times vect "vectorizing stmts using SLP" 2
FAIL: gcc.dg/vect/slp-35.c -flto -ffat-lto-objects  scan-tree-dump-times vect "vectorizing stmts using SLP" 1
FAIL: gcc.dg/vect/slp-35.c scan-tree-dump-times vect "vectorizing stmts using SLP" 1
XPASS: gcc.dg/vect/slp-reduc-3.c -flto -ffat-lto-objects  scan-tree-dump-times vect "vectorizing stmts using SLP" 1
XPASS: gcc.dg/vect/slp-reduc-3.c scan-tree-dump-times vect "vectorizing stmts using SLP" 1
FAIL: gcc.dg/vect/slp-reduc-4.c -flto -ffat-lto-objects  scan-tree-dump vect "vectorizing stmts using SLP"
FAIL: gcc.dg/vect/slp-reduc-4.c scan-tree-dump vect "vectorizing stmts using SLP"
FAIL: gcc.dg/vect/slp-reduc-7.c -flto -ffat-lto-objects execution test
FAIL: gcc.dg/vect/slp-reduc-7.c execution test
XPASS: gcc.dg/vect/vect-24.c -flto -ffat-lto-objects  scan-tree-dump-times vect "vectorized 3 loops" 1
XPASS: gcc.dg/vect/vect-24.c scan-tree-dump-times vect "vectorized 3 loops" 1
FAIL: gcc.dg/vect/vect-alias-check-4.c  (test for warnings, line 34)
FAIL: gcc.dg/vect/vect-alias-check-4.c  at line 19 (test for warnings, line 17)
FAIL: gcc.dg/vect/vect-alias-check-4.c  at line 27 (test for warnings, line 25)
FAIL: gcc.dg/vect/vect-alias-check-4.c (test for excess errors)
FAIL: gcc.dg/vect/vect-alias-check-4.c -flto -ffat-lto-objects  (test for warnings, line 34)
FAIL: gcc.dg/vect/vect-alias-check-4.c -flto -ffat-lto-objects  at line 19 (test for warnings, line 17)
FAIL: gcc.dg/vect/vect-alias-check-4.c -flto -ffat-lto-objects  at line 27 (test for warnings, line 25)
FAIL: gcc.dg/vect/vect-alias-check-4.c -flto -ffat-lto-objects (test for excess errors)
FAIL: gcc.dg/vect/vect-bic-bitmask-12.c -flto -ffat-lto-objects  scan-tree-dump dce7 "<=\\\\s*.+{ 255,.+}"
FAIL: gcc.dg/vect/vect-bic-bitmask-12.c scan-tree-dump dce7 "<=\\\\s*.+{ 255,.+}"
FAIL: gcc.dg/vect/vect-bic-bitmask-23.c -flto -ffat-lto-objects  scan-tree-dump dce7 "<=\\\\s*.+{ 255, 15, 1, 65535 }"
FAIL: gcc.dg/vect/vect-bic-bitmask-23.c scan-tree-dump dce7 "<=\\\\s*.+{ 255, 15, 1, 65535 }"
FAIL: gcc.dg/vect/vect-multitypes-11.c -flto -ffat-lto-objects  scan-tree-dump-times vect "vectorized 1 loops" 1
FAIL: gcc.dg/vect/vect-multitypes-11.c scan-tree-dump-times vect "vectorized 1 loops" 1

All of these are well understood.  For slp-reduc-7.c there is already a fix
posted and we will be needing a vsetvl pass fix after that.

Therefore, I'm going to push this to the trunk.

Note there are also a number of fortran vect failures that we haven't
looked at yet:

 		=== gfortran tests ===

Running target unix/-march=rv64gcv
FAIL: gfortran.dg/vect/O3-bb-slp-1.f   -O  (test for excess errors)
FAIL: gfortran.dg/vect/O3-bb-slp-2.f   -O  (test for excess errors)
FAIL: gfortran.dg/vect/O3-pr36119.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/O3-pr39595.f   -O  (test for excess errors)
FAIL: gfortran.dg/vect/Ofast-pr50414.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/cost-model-pr34445.f   -O  (test for excess errors)
FAIL: gfortran.dg/vect/cost-model-pr34445a.f   -O  (test for excess errors)
FAIL: gfortran.dg/vect/fast-math-pr38968.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/fast-math-real8-pr40801.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/fast-math-real8-pr40801.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/no-fre-no-copy-prop-O3-pr51704.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr100981-1.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr106253.f   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr107254.f90   -O0  (test for excess errors)
FAIL: gfortran.dg/vect/pr107254.f90   -O1  (test for excess errors)
FAIL: gfortran.dg/vect/pr107254.f90   -O2  (test for excess errors)
FAIL: gfortran.dg/vect/pr107254.f90   -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions  (test for excess errors)
FAIL: gfortran.dg/vect/pr107254.f90   -O3 -g  (test for excess errors)
FAIL: gfortran.dg/vect/pr107254.f90   -Os  (test for excess errors)
FAIL: gfortran.dg/vect/pr108979.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr33301.f   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr39318.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr46213.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr49955.f   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr50178.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr50412.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr51058-2.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr51058.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr51285.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr61171.f   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr62283.f   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr69466.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr69882.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr69980.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr70043.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr84913.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr85853.f90   -O0  (test for excess errors)
FAIL: gfortran.dg/vect/pr85853.f90   -O1  (test for excess errors)
FAIL: gfortran.dg/vect/pr85853.f90   -O2  (test for excess errors)
FAIL: gfortran.dg/vect/pr85853.f90   -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions  (test for excess errors)
FAIL: gfortran.dg/vect/pr85853.f90   -O3 -g  (test for excess errors)
FAIL: gfortran.dg/vect/pr85853.f90   -Os  (test for excess errors)
FAIL: gfortran.dg/vect/pr89535.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr90681.f   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr95403.f   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr96920.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr97761.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr99721.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr99746.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr99807.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr99825.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/pr99924.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/vect-5.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/vect-6.f   -O  (test for excess errors)
FAIL: gfortran.dg/vect/vect-9.f90   -O  (test for excess errors)
FAIL: gfortran.dg/vect/vect-alias-check-1.F90   -O0  (test for excess errors)
FAIL: gfortran.dg/vect/vect-alias-check-1.F90   -O1  (test for excess errors)
FAIL: gfortran.dg/vect/vect-alias-check-1.F90   -O2  (test for excess errors)
FAIL: gfortran.dg/vect/vect-alias-check-1.F90   -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions  (test for excess errors)
FAIL: gfortran.dg/vect/vect-alias-check-1.F90   -O3 -g  (test for excess errors)
FAIL: gfortran.dg/vect/vect-alias-check-1.F90   -Os  (test for excess errors)

Most (all?) of those are due to:
f951: Warning: command-line option '-Wno-psabi' is valid for C/C++/D/LTO/ObjC/ObjC++ but not for Fortran
so no real bug.

Regards
 Robin


  reply	other threads:[~2023-09-12 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 12:05 Juzhe-Zhong
2023-09-12 15:45 ` Robin Dapp [this message]
2023-09-12 19:41   ` Robin Dapp

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=d422422f-6e12-1f99-88bb-337e18a99ac7@gmail.com \
    --to=rdapp.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=juzhe.zhong@rivai.ai \
    --cc=kito.cheng@gmail.com \
    --cc=kito.cheng@sifive.com \
    /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).