public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: 钟居哲 <juzhe.zhong@rivai.ai>
To: rdapp.gcc <rdapp.gcc@gmail.com>,
	 gcc-patches <gcc-patches@gcc.gnu.org>,
	 palmer <palmer@dabbelt.com>,  kito.cheng <kito.cheng@gmail.com>,
	 "Jeff Law" <jeffreyalaw@gmail.com>
Cc: rdapp.gcc <rdapp.gcc@gmail.com>
Subject: Re: [PATCH] RISC-V: testsuite: Add rv64 requirement for bug-9 and bug-14.
Date: Tue, 21 Nov 2023 06:43:51 +0800	[thread overview]
Message-ID: <4606F5F6AEFA078C+2023112106435114237752@rivai.ai> (raw)
In-Reply-To: <1e713615-aba9-4f16-a38f-9b6658126415@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1787 bytes --]

/* { dg-do run { target { { {riscv_v} && {rv64} } } } } */

Seems you should remove rv64 here ? sicne I think it is redundant here.


juzhe.zhong@rivai.ai
 
From: Robin Dapp
Date: 2023-11-21 00:26
To: gcc-patches; palmer; Kito Cheng; jeffreyalaw; juzhe.zhong@rivai.ai
CC: rdapp.gcc
Subject: [PATCH] RISC-V: testsuite: Add rv64 requirement for bug-9 and bug-14.
Hi,
 
this adds an effective target requirement to compile the tests.  Since
we disabled 64-bit indices on rv32 targets those tests should be
unsupported on rv32.
 
Regards
Robin
 
gcc/testsuite/ChangeLog:
 
* g++.target/riscv/rvv/base/bug-14.C: Add
dg-require-effective-target rv64.
* g++.target/riscv/rvv/base/bug-9.C: Ditto.
---
gcc/testsuite/g++.target/riscv/rvv/base/bug-14.C | 1 +
gcc/testsuite/g++.target/riscv/rvv/base/bug-9.C  | 1 +
2 files changed, 2 insertions(+)
 
diff --git a/gcc/testsuite/g++.target/riscv/rvv/base/bug-14.C b/gcc/testsuite/g++.target/riscv/rvv/base/bug-14.C
index bf0c7bd3a36..0d35f2056c6 100644
--- a/gcc/testsuite/g++.target/riscv/rvv/base/bug-14.C
+++ b/gcc/testsuite/g++.target/riscv/rvv/base/bug-14.C
@@ -1,5 +1,6 @@
/* { dg-do run { target { { {riscv_v} && {rv64} } } } } */
/* { dg-options "-O2" } */
+/* { dg-require-effective-target rv64 } */
#include<cstdalign>
#include<cmath>
diff --git a/gcc/testsuite/g++.target/riscv/rvv/base/bug-9.C b/gcc/testsuite/g++.target/riscv/rvv/base/bug-9.C
index 8d17883bb57..4241f940d63 100644
--- a/gcc/testsuite/g++.target/riscv/rvv/base/bug-9.C
+++ b/gcc/testsuite/g++.target/riscv/rvv/base/bug-9.C
@@ -1,5 +1,6 @@
/* { dg-do run { target { { {riscv_v} && {rv64} } } } } */
/* { dg-options "-O2" } */
+/* { dg-require-effective-target rv64 } */
#include<cstdalign>
#include<cmath>
-- 
2.42.0
 

  reply	other threads:[~2023-11-20 22:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 16:26 Robin Dapp
2023-11-20 22:43 ` 钟居哲 [this message]
2023-11-21 13:36   ` Robin Dapp

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=4606F5F6AEFA078C+2023112106435114237752@rivai.ai \
    --to=juzhe.zhong@rivai.ai \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=kito.cheng@gmail.com \
    --cc=palmer@dabbelt.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).