From: Jeff Law <jeffreyalaw@gmail.com>
To: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
Robin Dapp <rdapp.gcc@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
palmer <palmer@dabbelt.com>, "kito.cheng" <kito.cheng@gmail.com>
Subject: Re: [PATCH] RISC-V/testsuite: Fix zvfh tests.
Date: Thu, 9 Nov 2023 18:11:05 -0700 [thread overview]
Message-ID: <f7de42fd-2d6d-4108-86af-012a7130829f@gmail.com> (raw)
In-Reply-To: <B10A6B07F85184EE+2023111009093106245330@rivai.ai>
On 11/9/23 18:09, juzhe.zhong@rivai.ai wrote:
> I am already using master branch.
>
> The FAIL is:
> xgcc: fatal error: Cannot find suitable multilib set for
> '-march=rv64imafdcv_zicsr_zifencei_zfhmin_zve32f_zve32x_zve64d_zve64f_zve64x_zvfh_zvl128b_zvl32b_zvl64b'/'-mabi=lp64d'
That's an multilib configuration issue of some kind. Changing binutils
isn't going to fix that.
jeff
next prev parent reply other threads:[~2023-11-10 1:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 15:21 Robin Dapp
2023-11-09 15:24 ` 钟居哲
2023-11-09 22:43 ` 钟居哲
2023-11-09 23:58 ` Jeff Law
2023-11-10 1:09 ` juzhe.zhong
2023-11-10 1:11 ` Jeff Law [this message]
2023-11-10 1:12 ` juzhe.zhong
2023-11-10 1:15 ` Jeff Law
2023-11-10 1:18 ` 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=f7de42fd-2d6d-4108-86af-012a7130829f@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).