public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jeff Law <law@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/riscv/heads/gcc-13-with-riscv-opts)] RISC-V: Make arch-24.c to test "success" case Date: Mon, 11 Sep 2023 13:33:40 +0000 (GMT) [thread overview] Message-ID: <20230911133340.C25123858296@sourceware.org> (raw) https://gcc.gnu.org/g:e8ec9036ff83010bb48e02e3b46e52acef33de9c commit e8ec9036ff83010bb48e02e3b46e52acef33de9c Author: Tsukasa OI <research_trasio@irq.a4lg.com> Date: Tue Aug 29 02:41:44 2023 +0000 RISC-V: Make arch-24.c to test "success" case arch-24.c and arch-25.c are exactly the same and redundant. The author suspects that the original author intended to test two base ISAs (RV32I and RV64I) so this commit changes arch-24.c to test that RV32I+Zcf does not cause any errors. gcc/testsuite/ChangeLog: * gcc.target/riscv/arch-24.c: Test RV32I+Zcf instead. (cherry picked from commit a248e1cc860821b96a42be96478257c4964a7c2a) Diff: --- gcc/testsuite/gcc.target/riscv/arch-24.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/gcc/testsuite/gcc.target/riscv/arch-24.c b/gcc/testsuite/gcc.target/riscv/arch-24.c index 3be4ade65a77..af15c3234b5e 100644 --- a/gcc/testsuite/gcc.target/riscv/arch-24.c +++ b/gcc/testsuite/gcc.target/riscv/arch-24.c @@ -1,5 +1,3 @@ /* { dg-do compile } */ -/* { dg-options "-march=rv64i_zcf -mabi=lp64" } */ +/* { dg-options "-march=rv32i_zcf -mabi=ilp32" } */ int foo() {} -/* { dg-error "'-march=rv64i_zcf': zcf extension supports in rv32 only" "" { target *-*-* } 0 } */ -/* { dg-error "'-march=rv64i_zca_zcf': zcf extension supports in rv32 only" "" { target *-*-* } 0 } */
reply other threads:[~2023-09-11 13:33 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230911133340.C25123858296@sourceware.org \ --to=law@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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).