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: Fix fail of vmv-imm-rv64.c in rv32
Date: Fri, 14 Jul 2023 02:35:34 +0000 (GMT)	[thread overview]
Message-ID: <20230714023534.217FB3857343@sourceware.org> (raw)

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

commit c408bd9199e99e1da651a6fc76316d443d5609fe
Author: Juzhe Zhong <juzhe.zhong@rivai.ai>
Date:   Fri May 12 14:38:46 2023 +0800

    RISC-V: Fix fail of vmv-imm-rv64.c in rv32
    
    After update local codebase to the trunk. I realize there is one more
    fail in RV32.
    After this patch, all fails of RVV are cleaned up.
    Thanks.
    
    FAIL: gcc.target/riscv/rvv/autovec/vmv-imm-rv64.c -O3 -ftree-vectorize
    (test for excess errors)
    Excess errors:
    cc1: error: ABI requires '-march=rv32'
    
    gcc/testsuite/ChangeLog:
    
            * gcc.target/riscv/rvv/autovec/vmv-imm-rv64.c: Add ABI
    
    Signed-off-by: Juzhe Zhong <juzhe.zhong@rivai.ai>

Diff:
---
 gcc/testsuite/gcc.target/riscv/rvv/autovec/vmv-imm-rv64.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.target/riscv/rvv/autovec/vmv-imm-rv64.c b/gcc/testsuite/gcc.target/riscv/rvv/autovec/vmv-imm-rv64.c
index 520321e1c73..e386166f95e 100644
--- a/gcc/testsuite/gcc.target/riscv/rvv/autovec/vmv-imm-rv64.c
+++ b/gcc/testsuite/gcc.target/riscv/rvv/autovec/vmv-imm-rv64.c
@@ -1,5 +1,5 @@
 /* { dg-do compile } */
-/* { dg-additional-options "-std=c99 -march=rv64gcv -fno-vect-cost-model --param=riscv-autovec-preference=scalable -fno-builtin" } */
+/* { dg-additional-options "-std=c99 -march=rv64gcv -mabi=lp64d -fno-vect-cost-model --param=riscv-autovec-preference=scalable -fno-builtin" } */
 
 #include "vmv-imm-template.h"

             reply	other threads:[~2023-07-14  2:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14  2:35 Jeff Law [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-25 23:19 Jeff Law

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=20230714023534.217FB3857343@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: 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).