From: Lehua Ding <lehua.ding@rivai.ai>
To: gcc-patches@gcc.gnu.org
Cc: juzhe.zhong@rivai.ai, rdapp.gcc@gmail.com, kito.cheng@gmail.com,
palmer@rivosinc.com, jeffreyalaw@gmail.com
Subject: [PATCH] RISC-V: Remove testcase that cannot be compiled because VLEN limitation
Date: Tue, 18 Jul 2023 14:55:11 +0800 [thread overview]
Message-ID: <20230718065512.2728118-1-lehua.ding@rivai.ai> (raw)
Hi,
Since the latter patch (https://gcc.gnu.org/pipermail/gcc-patches/2023-July/624689.html)
forbidden VLEN > 4096, the testcase attribute-20.c is no long need. This is obvious.
Best,
Lehua
gcc/testsuite/ChangeLog:
* gcc.target/riscv/attribute-20.c: Removed.
---
gcc/testsuite/gcc.target/riscv/attribute-20.c | 7 -------
1 file changed, 7 deletions(-)
delete mode 100644 gcc/testsuite/gcc.target/riscv/attribute-20.c
diff --git a/gcc/testsuite/gcc.target/riscv/attribute-20.c b/gcc/testsuite/gcc.target/riscv/attribute-20.c
deleted file mode 100644
index f7d0b29b71c..00000000000
--- a/gcc/testsuite/gcc.target/riscv/attribute-20.c
+++ /dev/null
@@ -1,7 +0,0 @@
-/* { dg-do compile } */
-/* { dg-options "-march=rv64gcv_zvl65536b -mabi=lp64d" } */
-int foo()
-{
-}
-
-/* { dg-final { scan-assembler ".attribute arch, \"rv64i2p1_m2p0_a2p1_f2p2_d2p2_c2p0_v1p0_zicsr2p0_zifencei2p0_zve32f1p0_zve32x1p0_zve64d1p0_zve64f1p0_zve64x1p0_zvl1024b1p0_zvl128b1p0_zvl16384b1p0_zvl2048b1p0_zvl256b1p0_zvl32768b1p0_zvl32b1p0_zvl4096b1p0_zvl512b1p0_zvl64b1p0_zvl65536b1p0_zvl8192b1p0\"" } } */
--
2.36.3
next reply other threads:[~2023-07-18 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 6:55 Lehua Ding [this message]
2023-07-18 6:55 ` juzhe.zhong
2023-07-18 7:03 ` =?gb18030?B?TGVodWEgRGluZw==?=
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=20230718065512.2728118-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).