public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] RISC-V: Fix riscv/arch-19.c with different ISA spec version
Date: Mon, 19 Feb 2024 21:50:44 +0000 (GMT)	[thread overview]
Message-ID: <20240219215044.949033858D35@sourceware.org> (raw)

https://gcc.gnu.org/g:e4e63fa0bb34a52b4bd4daa4bb5211bc25e7f584

commit e4e63fa0bb34a52b4bd4daa4bb5211bc25e7f584
Author: Kito Cheng <kito.cheng@sifive.com>
Date:   Mon Feb 19 18:01:48 2024 -0300

    RISC-V: Fix riscv/arch-19.c with different ISA spec version
    
    In newer ISA spec, F will implied zicsr, add that into -march option to
    prevent different test result on different default -misa-spec version.
    
    gcc/testsuite/
    
            * gcc.target/riscv/arch-19.c: Add -misa-spec.
    
    (cherry picked from commit 9fde76a3be8e1717d9d38492c40675e742611e45)

Diff:
---
 gcc/testsuite/gcc.target/riscv/arch-19.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/testsuite/gcc.target/riscv/arch-19.c b/gcc/testsuite/gcc.target/riscv/arch-19.c
index b042e1a49fe6..95204ede26a6 100644
--- a/gcc/testsuite/gcc.target/riscv/arch-19.c
+++ b/gcc/testsuite/gcc.target/riscv/arch-19.c
@@ -1,4 +1,4 @@
 /* { dg-do compile } */
-/* { dg-options "-march=rv64if_zfinx -mabi=lp64" } */
+/* { dg-options "-march=rv64if_zicsr_zfinx -mabi=lp64" } */
 int foo() {}
-/* { dg-error "'-march=rv64if_zfinx': z\\*inx conflicts with floating-point extensions" "" { target *-*-* } 0 } */
+/* { dg-error "'-march=rv64if_zicsr_zfinx': z\\*inx conflicts with floating-point extensions" "" { target *-*-* } 0 } */

             reply	other threads:[~2024-02-19 21:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19 21:50 Alexandre Oliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-19 21:40 Alexandre Oliva

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=20240219215044.949033858D35@sourceware.org \
    --to=aoliva@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: 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).