From: Robin Dapp <rdapp.gcc@gmail.com>
To: Lehua Ding <lehua.ding@rivai.ai>,
"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>
Cc: rdapp.gcc@gmail.com
Subject: Re: [PATCH] RISC-V: testsuite: Fix 32-bit FAILs.
Date: Mon, 13 Nov 2023 11:17:40 +0100 [thread overview]
Message-ID: <5e4ed623-d793-4fc1-9d32-cd8070c0444e@gmail.com> (raw)
In-Reply-To: <4F2BF54C1D97ABBC+4118c01f-5f50-4ea5-9a21-7e6afeb86686@rivai.ai>
> Looks like your configure is --with-march=rv32gcv_zvfh, can you change to --with-march=rv32gcv_zvfh_zfh?
From config.log:
$ ../configure --prefix=/home/rdapp/projects/builds/gcc --target=riscv32-unknown-linux-gnu --disable-nls --disable-multilib --disable-bootstrap --with-sysroot=/home/rdapp/projects/x-tools/riscv32-unknown-linux-gnu/riscv32-unknown-linux-gnu/sysroot --disable-libsanitizer --with-arch=rv32gcv_zfh_zvfh --with-abi=ilp32d --enable-languages=c,c++
How do you invoke the testsuite and which target board?
Regards
Robin
next prev parent reply other threads:[~2023-11-13 10:17 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 [this message]
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
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=5e4ed623-d793-4fc1-9d32-cd8070c0444e@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=lehua.ding@rivai.ai \
--cc=palmer@dabbelt.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).