From: Lehua Ding <lehua.ding@rivai.ai>
To: Robin Dapp <rdapp.gcc@gmail.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
gcc-patches <gcc-patches@gcc.gnu.org>,
palmer <palmer@dabbelt.com>, "kito.cheng" <kito.cheng@gmail.com>,
jeffreyalaw <jeffreyalaw@gmail.com>
Subject: Re: [PATCH] RISC-V: testsuite: Fix 32-bit FAILs.
Date: Mon, 13 Nov 2023 18:35:29 +0800 [thread overview]
Message-ID: <65B832CB12B587BC+4f42ba3f-f41b-48db-87a5-63ea88ba7ff3@rivai.ai> (raw)
In-Reply-To: <8ec62cf5-e867-4984-a1c6-e532c643c1e9@gmail.com>
On 2023/11/13 18:33, Robin Dapp wrote:
>> On 2023/11/13 18:22, juzhe.zhong@rivai.ai wrote:
>>> If there is a difference between them. I think we should fix riscv-common.cc.
>>> Since I think "zvfh_zfh" should not be different with "zfh_zvfh"
>>
>> It's possible. Let me debug it and see if there's a problem.
>
> I don't think it is different. Just checked and it still works for me.
>
> Could you please tell me how you invoke the testsuite?
We use the riscv-gnu-toolchain and run this `make report-newlib
SIM=spike RUNTESTFLAGS="rvv.exp" -j100`
--
Best,
Lehua (RiVAI)
lehua.ding@rivai.ai
next prev parent reply other threads:[~2023-11-13 10:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 12:51 Robin Dapp
2023-11-10 13:26 ` 钟居哲
2023-11-10 23:00 ` 钟居哲
2023-11-13 8:52 ` Robin Dapp
2023-11-13 8:55 ` juzhe.zhong
2023-11-13 9:10 ` Robin Dapp
2023-11-13 9:31 ` Robin Dapp
2023-11-13 9:34 ` juzhe.zhong
2023-11-13 9:49 ` Lehua Ding
2023-11-13 9:59 ` Robin Dapp
2023-11-13 10:14 ` Lehua Ding
2023-11-13 10:17 ` Robin Dapp
2023-11-13 10:22 ` juzhe.zhong
2023-11-13 10:32 ` Lehua Ding
2023-11-13 10:33 ` Robin Dapp
2023-11-13 10:35 ` Lehua Ding [this message]
2023-11-13 11:13 ` Lehua Ding
2023-11-13 11:27 ` Lehua Ding
2023-11-15 10:47 ` 钟居哲
2023-11-17 8:29 ` Kito Cheng
2023-11-17 8:54 ` Lehua Ding
2023-11-17 8:56 ` Robin Dapp
2023-11-13 8:58 ` juzhe.zhong
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=65B832CB12B587BC+4f42ba3f-f41b-48db-87a5-63ea88ba7ff3@rivai.ai \
--to=lehua.ding@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.com \
--cc=rdapp.gcc@gmail.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).