public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: 钟居哲 <juzhe.zhong@rivai.ai>
To: "Jeff Law" <jeffreyalaw@gmail.com>,
	 gcc-patches <gcc-patches@gcc.gnu.org>
Cc: kito.cheng <kito.cheng@sifive.com>,  palmer <palmer@rivosinc.com>,
	 rdapp.gcc <rdapp.gcc@gmail.com>
Subject: Re: Re: [PATCH] RISC-V: Fix fails of testcases
Date: Tue, 20 Jun 2023 07:15:23 +0800	[thread overview]
Message-ID: <C0261E7FCF3DE607+2023062007152323846451@rivai.ai> (raw)
In-Reply-To: <628a0086-fead-989b-caf2-eef91cbb9761@gmail.com>

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

>> Presumably the target selector in the dg-do ensures we only build/run
>> these on the appropriate targets now and we don't need explicitly -march
>> arguments?
Yes. 

>> Assuming that's correct, this is fine for the trunk.
Thanks.


juzhe.zhong@rivai.ai
 
From: Jeff Law
Date: 2023-06-20 07:13
To: Juzhe-Zhong; gcc-patches
CC: kito.cheng; palmer; rdapp.gcc
Subject: Re: [PATCH] RISC-V: Fix fails of testcases
 
 
On 6/19/23 17:04, Juzhe-Zhong wrote:
> FAIL: gcc.target/riscv/rvv/autovec/vls-vlmax/vec_extract-run.c -std=c99 -O3 -ftree-vectorize --param riscv-autovec-preference=fixed-vlmax (test for excess errors)
> Excess errors:
> xgcc: fatal error: Cannot find suitable multilib set for '-march=rv64imafdcv_zicsr_zifencei_zve32f_zve32x_zve64d_zve64f_zve64x_zvl128b_zvl32b_zvl64b'/'-mabi=lp64d'
> compilation terminated.
> 
> gcc/testsuite/ChangeLog:
> 
>          * gcc.target/riscv/rvv/autovec/vls-vlmax/vec_extract-run.c: Fix fail.
>          * gcc.target/riscv/rvv/autovec/vls-vlmax/vec_extract-zvfh-run.c: Ditto.
>          * gcc.target/riscv/rvv/autovec/vls-vlmax/vec_set-run.c: Ditto.
>          * gcc.target/riscv/rvv/autovec/vls-vlmax/vec_set-zvfh-run.c: Ditto.
Presumably the target selector in the dg-do ensures we only build/run 
these on the appropriate targets now and we don't need explicitly -march 
arguments?
 
Assuming that's correct, this is fine for the trunk.
 
jeff
 

  reply	other threads:[~2023-06-19 23:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19 23:04 Juzhe-Zhong
2023-06-19 23:13 ` Jeff Law
2023-06-19 23:15   ` 钟居哲 [this message]
2023-06-20  1:18     ` 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=C0261E7FCF3DE607+2023062007152323846451@rivai.ai \
    --to=juzhe.zhong@rivai.ai \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=kito.cheng@sifive.com \
    --cc=palmer@rivosinc.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).