public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: jeffreyalaw <jeffreyalaw@gmail.com>,
	 "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: Re: [PATCH] RISC-V/testsuite: Fix zvfh tests.
Date: Fri, 10 Nov 2023 09:12:53 +0800	[thread overview]
Message-ID: <9838F8C140260D88+2023111009125279475631@rivai.ai> (raw)
In-Reply-To: <f7de42fd-2d6d-4108-86af-012a7130829f@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 673 bytes --]

How to fix it ? I am pretty noob on testing CI.
Can Robin fix that?



juzhe.zhong@rivai.ai
 
From: Jeff Law
Date: 2023-11-10 09:11
To: juzhe.zhong@rivai.ai; Robin Dapp; gcc-patches; palmer; kito.cheng
Subject: Re: [PATCH] RISC-V/testsuite: Fix zvfh tests.
 
 
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
 

  reply	other threads:[~2023-11-10  1:13 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
2023-11-10  1:12         ` juzhe.zhong [this message]
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=9838F8C140260D88+2023111009125279475631@rivai.ai \
    --to=juzhe.zhong@rivai.ai \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --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).