public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robin Dapp <rdapp.gcc@gmail.com>
To: "Lehua Ding" <lehua.ding@rivai.ai>, "pan2.li" <pan2.li@intel.com>,
	"Jeff Law" <jeffreyalaw@gmail.com>, 钟居哲 <juzhe.zhong@rivai.ai>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Cc: rdapp.gcc@gmail.com, "yanzhang.wang" <yanzhang.wang@intel.com>,
	"kito.cheng" <kito.cheng@gmail.com>, palmer <palmer@rivosinc.com>
Subject: Re: [PATCH] RISC-V: Add tuple vector mode psABI checking and simplify code
Date: Tue, 20 Jun 2023 15:50:25 +0200	[thread overview]
Message-ID: <d7261be6-16e9-7ce4-1803-9c3bf1196dee@gmail.com> (raw)
In-Reply-To: <tencent_32E3A2090CA54707320946A2@qq.com>

> By the way, shouldn't these cases have the `-mabi=lp64d` option added,
> otherwise I get the following failure message when I run tests on RV32 GCC.
> 
>   FAIL: gcc.target/riscv/rvv/autovec/vls-vlmax/vec_set-1.c -std=c99 -O3 -ftree-vectorize --param riscv-autovec-preference=fixed-vlmax (test for excess errors)
>   Excess errors.
>   cc1: error: ABI requires '-march=rv32'

Arg, yes definitely, sorry.  I keep forgetting this... Will fix.

Regards
 Robin


  reply	other threads:[~2023-06-20 13:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-18 11:41 Lehua Ding
2023-06-18 13:16 ` 钟居哲
2023-06-19 18:03   ` Jeff Law
2023-06-20  1:16     ` Li, Pan2
2023-06-20 12:10       ` Robin Dapp
2023-06-20 12:58         ` Lehua Ding
2023-06-20 13:01           ` Robin Dapp
2023-06-20 13:13             ` Lehua Ding
2023-06-20 13:44         ` Lehua Ding
2023-06-20 13:50           ` Robin Dapp [this message]
2023-06-20 14:03           ` 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=d7261be6-16e9-7ce4-1803-9c3bf1196dee@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=lehua.ding@rivai.ai \
    --cc=palmer@rivosinc.com \
    --cc=pan2.li@intel.com \
    --cc=yanzhang.wang@intel.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).