From: Robin Dapp <rdapp.gcc@gmail.com>
To: Patrick O'Neill <patrick@rivosinc.com>,
Juzhe-Zhong <juzhe.zhong@rivai.ai>,
gcc-patches@gcc.gnu.org
Cc: rdapp.gcc@gmail.com, Kito Cheng <kito.cheng@gmail.com>
Subject: Re: [Ready to commit V3] RISC-V: Add AVL propagation PASS for RVV auto-vectorization
Date: Thu, 26 Oct 2023 20:15:37 +0200 [thread overview]
Message-ID: <08962e5c-8741-449d-8c80-08990dcb84c4@gmail.com> (raw)
In-Reply-To: <7b2dae40-bc25-5285-1258-f1b37f130ba4@rivosinc.com>
> rv32gcv:
> FAIL: gfortran.dg/intrinsic_pack_6.f90 -O2 execution test
> FAIL: gfortran.dg/intrinsic_pack_6.f90 -O3 -g execution test
> FAIL: gfortran.dg/matmul_3.f90 -O2 execution test
> FAIL: gfortran.fortran-torture/execute/intrinsic_matmul.f90 execution, -O2
> FAIL: gfortran.fortran-torture/execute/intrinsic_matmul.f90 execution, -O2 -fbounds-check
> FAIL: gfortran.fortran-torture/execute/intrinsic_matmul.f90 execution, -O2 -fomit-frame-pointer -finline-functions
> FAIL: gfortran.fortran-torture/execute/intrinsic_matmul.f90 execution, -O3 -g
>
> rv64gcv:
> FAIL: gfortran.dg/matmul_6.f90 -O2 execution test
Those might also flip flop, I have them seen FAIL and PASS before
randomly. It looks like there is at least 10 of those, really need
to figure out the root cause...
Regards
Robin
next prev parent reply other threads:[~2023-10-26 18:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 8:13 Juzhe-Zhong
2023-10-26 18:12 ` Patrick O'Neill
2023-10-26 18:15 ` Robin Dapp [this message]
2023-10-26 18:43 ` Patrick O'Neill
2023-10-27 1:13 ` juzhe.zhong
2023-10-26 23:05 ` 钟居哲
2023-10-28 8:15 ` Andreas Schwab
2023-10-29 12:08 ` Li, Pan2
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=08962e5c-8741-449d-8c80-08990dcb84c4@gmail.com \
--to=rdapp.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=patrick@rivosinc.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).