From: Lehua Ding <lehua.ding@rivai.ai>
To: gcc-patches@gcc.gnu.org
Cc: juzhe.zhong@rivai.ai, kito.cheng@gmail.com, rdapp.gcc@gmail.com,
palmer@rivosinc.com, jeffreyalaw@gmail.com
Subject: [PATCH] RISC-V: Fix -march error of zhinxmin testcases
Date: Fri, 18 Aug 2023 10:59:11 +0800 [thread overview]
Message-ID: <20230818025911.1281907-1-lehua.ding@rivai.ai> (raw)
This little patch fixs the -march error of a zhinxmin testcase I added earlier
and an old zhinxmin testcase, since these testcases are for zhinxmin extension
and not zfhmin extension.
---
gcc/testsuite/gcc.target/riscv/_Float16-zhinxmin-3.c | 2 +-
gcc/testsuite/gcc.target/riscv/_Float16-zhinxmin-4.c | 5 +++--
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/gcc/testsuite/gcc.target/riscv/_Float16-zhinxmin-3.c b/gcc/testsuite/gcc.target/riscv/_Float16-zhinxmin-3.c
index 7a43641a5a6..939b3787383 100644
--- a/gcc/testsuite/gcc.target/riscv/_Float16-zhinxmin-3.c
+++ b/gcc/testsuite/gcc.target/riscv/_Float16-zhinxmin-3.c
@@ -1,5 +1,5 @@
/* { dg-do compile } */
-/* { dg-options "-march=rv64if_zfhmin -mabi=lp64f -O" } */
+/* { dg-options "-march=rv64i_zhinxmin -mabi=lp64 -O" } */
int foo1 (_Float16 a, _Float16 b)
{
diff --git a/gcc/testsuite/gcc.target/riscv/_Float16-zhinxmin-4.c b/gcc/testsuite/gcc.target/riscv/_Float16-zhinxmin-4.c
index 4ac49228898..ebc615a483f 100644
--- a/gcc/testsuite/gcc.target/riscv/_Float16-zhinxmin-4.c
+++ b/gcc/testsuite/gcc.target/riscv/_Float16-zhinxmin-4.c
@@ -1,11 +1,12 @@
/* { dg-do compile } */
-/* { dg-options "-march=rv64if_zfhmin -mabi=lp64 -O3 -mcmodel=medany" } */
+/* { dg-options "-march=rv64i_zhinxmin -mabi=lp64 -O3 -mcmodel=medany" } */
/* { dg-final { check-function-bodies "**" "" } } */
/* Make sure zfhmin behaves the same way as zfh. */
/*
** foo: { target { no-opts "-flto" } }
-** lh\ta0,\.LC0
+** lla\ta[0-9]+,\.LC0
+** lhu\ta[0-9]+,0\(a[0-9]+\)
** ...
*/
_Float16 foo() { return 0.8974; }
--
2.36.3
next reply other threads:[~2023-08-18 2:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 2:59 Lehua Ding [this message]
2023-08-18 6:39 ` Robin Dapp
2023-08-18 7:16 ` Lehua Ding
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=20230818025911.1281907-1-lehua.ding@rivai.ai \
--to=lehua.ding@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.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).