From: Jeff Law <jeffreyalaw@gmail.com>
To: juzhe.zhong@rivai.ai, gcc-patches@gcc.gnu.org
Cc: schwab@linux-m68k.org, kito.cheng@gmail.com
Subject: Re: [PATCH] RISC-V: Fix RVV testcases.
Date: Mon, 31 Oct 2022 16:00:49 -0600 [thread overview]
Message-ID: <87e80ca7-2d66-09b1-26e3-fe64c6553b28@gmail.com> (raw)
In-Reply-To: <20221031014022.250112-1-juzhe.zhong@rivai.ai>
On 10/30/22 19:40, juzhe.zhong@rivai.ai wrote:
> From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/rvv/base/abi-2.c: Change ilp32d to ilp32.
> * gcc.target/riscv/rvv/base/abi-3.c: Ditto.
> * gcc.target/riscv/rvv/base/abi-4.c: Ditto.
> * gcc.target/riscv/rvv/base/abi-5.c: Ditto.
> * gcc.target/riscv/rvv/base/abi-6.c: Ditto.
> * gcc.target/riscv/rvv/base/abi-7.c: Ditto.
> * gcc.target/riscv/rvv/base/mov-1.c: Ditto.
> * gcc.target/riscv/rvv/base/mov-10.c: Ditto.
> * gcc.target/riscv/rvv/base/mov-11.c: Ditto.
> * gcc.target/riscv/rvv/base/mov-12.c: Ditto.
> * gcc.target/riscv/rvv/base/mov-13.c: Ditto.
> * gcc.target/riscv/rvv/base/mov-2.c: Ditto.
> * gcc.target/riscv/rvv/base/mov-3.c: Ditto.
> * gcc.target/riscv/rvv/base/mov-4.c: Ditto.
> * gcc.target/riscv/rvv/base/mov-5.c: Ditto.
> * gcc.target/riscv/rvv/base/mov-6.c: Ditto.
> * gcc.target/riscv/rvv/base/mov-7.c: Ditto.
> * gcc.target/riscv/rvv/base/mov-8.c: Ditto.
> * gcc.target/riscv/rvv/base/mov-9.c: Ditto.
> * gcc.target/riscv/rvv/base/pragma-1.c: Ditto.
> * gcc.target/riscv/rvv/base/user-1.c: Ditto.
> * gcc.target/riscv/rvv/base/user-2.c: Ditto.
> * gcc.target/riscv/rvv/base/user-3.c: Ditto.
> * gcc.target/riscv/rvv/base/user-4.c: Ditto.
> * gcc.target/riscv/rvv/base/user-5.c: Ditto.
> * gcc.target/riscv/rvv/base/user-6.c: Ditto.
> * gcc.target/riscv/rvv/base/vsetvl-1.c: Ditto.
I'm pretty new to the RISC-V world, but don't some of the cases
(particularly the abi-* tests) verify that the ABI specification does
not override the arch specification WRT availability of types?
Jeff
next prev parent reply other threads:[~2022-10-31 22:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 1:40 juzhe.zhong
2022-10-31 22:00 ` Jeff Law [this message]
2022-10-31 22:25 ` 钟居哲
2022-10-31 22:30 ` Palmer Dabbelt
2022-10-31 23:52 ` 钟居哲
2022-11-01 18:35 ` Palmer Dabbelt
2022-11-06 0:13 ` Kito Cheng
2022-11-18 20:07 ` Jeff Law
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=87e80ca7-2d66-09b1-26e3-fe64c6553b28@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=schwab@linux-m68k.org \
/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).