public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robin Dapp <rdapp.gcc@gmail.com>
To: Juzhe-Zhong <juzhe.zhong@rivai.ai>, gcc-patches@gcc.gnu.org
Cc: rdapp.gcc@gmail.com, kito.cheng@gmail.com, kito.cheng@sifive.com,
	jeffreyalaw@gmail.com
Subject: Re: [PATCH V6] RISC-V: Enable vec_int testsuite for RVV VLA vectorization
Date: Tue, 12 Sep 2023 21:41:23 +0200	[thread overview]
Message-ID: <8aec46da-fc97-3fec-ff31-fd0bf11b4e3f@gmail.com> (raw)
In-Reply-To: <d422422f-6e12-1f99-88bb-337e18a99ac7@gmail.com>

> Most (all?) of those are due to:
> f951: Warning: command-line option '-Wno-psabi' is valid for C/C++/D/LTO/ObjC/ObjC++ but not for Fortran
> so no real bug.

When pushing this, I'd take the liberty of enabling the recently merged vector
ABI so we don't require -Wno-psabi anymore.  All Fortran FAILs disappear and
nothing else changes.

--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -11166,12 +11166,12 @@ proc check_vect_support_and_set_flags { } {
     } elseif [istarget riscv64-*-*] {
        if [check_effective_target_riscv_vector_hw] {
            lappend DEFAULT_VECTCFLAGS "--param" "riscv-autovec-preference=scalable"
-           lappend DEFAULT_VECTCFLAGS "-Wno-psabi"
+           lappend DEFAULT_VECTCFLAGS "--param" "riscv-vector-abi"
            set dg-do-what-default run
        } else {
            lappend DEFAULT_VECTCFLAGS "-march=rv64gcv_zvfh" "-mabi=lp64d"
            lappend DEFAULT_VECTCFLAGS "--param" "riscv-autovec-preference=scalable"
-           lappend DEFAULT_VECTCFLAGS "-Wno-psabi"
+           lappend DEFAULT_VECTCFLAGS "--param" "riscv-vector-abi"
            set dg-do-what-default compile
        }
     } else {

Regards
 Robin


      reply	other threads:[~2023-09-12 19:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 12:05 Juzhe-Zhong
2023-09-12 15:45 ` Robin Dapp
2023-09-12 19:41   ` Robin Dapp [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=8aec46da-fc97-3fec-ff31-fd0bf11b4e3f@gmail.com \
    --to=rdapp.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=juzhe.zhong@rivai.ai \
    --cc=kito.cheng@gmail.com \
    --cc=kito.cheng@sifive.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).