public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Patrick O'Neill <patrick@rivosinc.com>
To: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [Committed] RISC-V: Add require-effective-target to pr113429 testcase
Date: Mon, 29 Jan 2024 09:51:01 -0800	[thread overview]
Message-ID: <8c70acae-e255-4e71-bc74-b180cf0ad6d8@rivosinc.com> (raw)
In-Reply-To: <09B972E03F3130F8+202401291141029620130@rivai.ai>

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

Committed.

Thanks for catching this.
Patrick

On 1/28/24 19:41, juzhe.zhong@rivai.ai wrote:
> ok
>
>
> ------------------------------------------------------------------------
> juzhe.zhong@rivai.ai
>
>     *From:* Patrick O'Neill <mailto:patrick@rivosinc.com>
>     *Date:* 2024-01-27 10:50
>     *To:* gcc-patches <mailto:gcc-patches@gcc.gnu.org>
>     *CC:* juzhe.zhong <mailto:juzhe.zhong@rivai.ai>; Patrick O'Neill
>     <mailto:patrick@rivosinc.com>
>     *Subject:* [PATCH] RISC-V: Add require-effective-target to
>     pr113429 testcase
>     The pr113429 testcase fails with newlib spike runs. Adding
>     require-effective-target rv64 and riscv_v fixes the issue.
>     gcc/testsuite/ChangeLog:
>     * gcc.target/riscv/rvv/vsetvl/pr113429.c: Add
>     require-effective-target rv64 and riscv_v
>     Signed-off-by: Patrick O'Neill <patrick@rivosinc.com>
>     ---
>     Tested using rv64gc newlib spike.
>     ---
>     gcc/testsuite/gcc.target/riscv/rvv/vsetvl/pr113429.c | 2 ++
>     1 file changed, 2 insertions(+)
>     diff --git a/gcc/testsuite/gcc.target/riscv/rvv/vsetvl/pr113429.c
>     b/gcc/testsuite/gcc.target/riscv/rvv/vsetvl/pr113429.c
>     index 05c3eeecb94..a7f5db616d8 100644
>     --- a/gcc/testsuite/gcc.target/riscv/rvv/vsetvl/pr113429.c
>     +++ b/gcc/testsuite/gcc.target/riscv/rvv/vsetvl/pr113429.c
>     @@ -1,5 +1,7 @@
>     /* { dg-do run } */
>     /* { dg-options "-march=rv64gcv_zvl256b -mabi=lp64d -O3" } */
>     +/* { dg-require-effective-target rv64 } */
>     +/* { dg-require-effective-target riscv_v } */
>     long a;
>     int b, c, d, e, f, g;
>     -- 
>     2.34.1
>

      reply	other threads:[~2024-01-29 17:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-27  2:50 [PATCH] " Patrick O'Neill
2024-01-29  3:41 ` juzhe.zhong
2024-01-29 17:51   ` Patrick O'Neill [this message]

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=8c70acae-e255-4e71-bc74-b180cf0ad6d8@rivosinc.com \
    --to=patrick@rivosinc.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=juzhe.zhong@rivai.ai \
    /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).