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/111311] RISC-V regression testsuite errors with --param=riscv-autovec-preference=scalable Date: Wed, 08 Nov 2023 01:42:00 +0000 [thread overview] Message-ID: <bug-111311-4-hvAf4pYz1D@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111311-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111311 --- Comment #15 from JuzheZhong <juzhe.zhong at rivai dot ai> --- Update status: There are only these following dump FAILs: FAIL: gcc.dg/signbit-2.c scan-tree-dump optimized "\\s+>\\s+{ 0(, 0)+ }" FAIL: gcc.dg/signbit-2.c scan-tree-dump-not optimized "\\s+>>\\s+31" XPASS: gcc.dg/uninit-pred-9_b.c bogus warning (test for bogus messages, line 20) FAIL: gcc.dg/var-expand1.c scan-rtl-dump loop2_unroll "Expanding Accumulator" FAIL: gcc.dg/tree-ssa/gen-vect-34.c scan-tree-dump-times vect "vectorized 1 loops" 1 FAIL: gcc.dg/tree-ssa/loop-bound-1.c scan-tree-dump ivopts "bounded by 254" FAIL: gcc.dg/tree-ssa/loop-bound-2.c scan-tree-dump ivopts "bounded by 254" XPASS: gcc.dg/tree-ssa/pr84512.c scan-tree-dump optimized "return 285;" FAIL: gcc.dg/tree-ssa/predcom-4.c scan-tree-dump-times pcom "Combination" 1 FAIL: gcc.dg/tree-ssa/predcom-4.c scan-tree-dump-times pcom "Unrolling 3 times." 1 FAIL: gcc.dg/tree-ssa/predcom-5.c scan-tree-dump-times pcom "Combination" 2 FAIL: gcc.dg/tree-ssa/predcom-5.c scan-tree-dump-times pcom "Unrolling 3 times." 1 FAIL: gcc.dg/tree-ssa/predcom-9.c scan-tree-dump pcom "Executing predictive commoning without unrolling" FAIL: gcc.dg/tree-ssa/reassoc-46.c scan-tree-dump-times optimized "(?:vect_)?sum_[\\d._]+ = (?:(?:vect_)?_[\\d._]+ \\+ (?:vect_)?sum_[\\d._]+|(?:vect_)?sum_[\\d._]+ \\+ (?:vect_)?_[\\d._]+)" 1 FAIL: gcc.dg/tree-ssa/scev-10.c scan-tree-dump-times ivopts " Type:\\tREFERENCE ADDRESS\n" 1 FAIL: gcc.dg/tree-ssa/scev-11.c scan-tree-dump-times ivopts " Type:\\tREFERENCE ADDRESS\n" 2 FAIL: gcc.dg/tree-ssa/scev-14.c scan-tree-dump ivopts "Overflowness wrto loop niter:\tNo-overflow" FAIL: gcc.dg/tree-ssa/scev-9.c scan-tree-dump-times ivopts " Type:\\tREFERENCE ADDRESS\n" 1 FAIL: gcc.dg/tree-ssa/split-path-11.c scan-tree-dump-times split-paths "join point for if-convertable half-diamond" 1 Confirm these FAILs also happen on ARM SVE and they don't fix them. So, it doesn't make sense we dedicate efforts to fix them. Just ignore them. Other than that, we have 2 more FAILs in vect testsuite, these 2 patches will fix them: https://gcc.gnu.org/pipermail/gcc-patches/2023-November/635589.html https://gcc.gnu.org/pipermail/gcc-patches/2023-November/635591.html After these 2 patches, no dump FAILs need to be fixed, just ignore other dump FAILs should be reasonable. Then, we move forward to fix execution FAILs.
next prev parent reply other threads:[~2023-11-08 1:42 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-06 21:10 [Bug target/111311] New: " rdapp at gcc dot gnu.org 2023-09-06 22:25 ` [Bug target/111311] " juzhe.zhong at rivai dot ai 2023-09-06 22:37 ` juzhe.zhong at rivai dot ai 2023-09-07 7:56 ` juzhe.zhong at rivai dot ai 2023-09-08 8:51 ` juzhe.zhong at rivai dot ai 2023-09-10 2:14 ` cvs-commit at gcc dot gnu.org 2023-09-11 3:32 ` cvs-commit at gcc dot gnu.org 2023-09-11 13:21 ` cvs-commit at gcc dot gnu.org 2023-11-02 17:12 ` patrick at rivosinc dot com 2023-11-02 17:18 ` vineetg at gcc dot gnu.org 2023-11-02 18:46 ` rdapp at gcc dot gnu.org 2023-11-02 21:23 ` vineetg at gcc dot gnu.org 2023-11-02 22:31 ` juzhe.zhong at rivai dot ai 2023-11-02 22:47 ` pinskia at gcc dot gnu.org 2023-11-03 2:56 ` law at gcc dot gnu.org 2023-11-08 1:42 ` juzhe.zhong at rivai dot ai [this message] 2023-11-08 20:12 ` vineetg at gcc dot gnu.org 2023-11-14 20:55 ` ewlu at rivosinc dot com 2023-11-15 23:39 ` patrick at rivosinc dot com 2023-11-16 1:08 ` juzhe.zhong at rivai dot ai 2023-11-16 1:15 ` 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-111311-4-hvAf4pYz1D@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: linkBe 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).