From: Robin Dapp <rdapp.gcc@gmail.com>
To: Kito Cheng <kito.cheng@gmail.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"Kito.cheng" <kito.cheng@sifive.com>,
palmer <palmer@rivosinc.com>, jeffreyalaw <jeffreyalaw@gmail.com>
Subject: Re: [PATCH] RISC-V: Fix RVV binary auto-vectorizaiton test fails
Date: Fri, 12 May 2023 08:34:17 +0200 [thread overview]
Message-ID: <4b6ae646-d2d6-c84b-9d86-3e5ca80b3cbf@gmail.com> (raw)
In-Reply-To: <CA+yXCZBuFTD6Cq7zUE9Cs-BE=Nw3WJBSrmjQeMK4A-GoGL3=Sw@mail.gmail.com>
> ok, thanks :)
This has likely been discussed at length before, but why need to
specify the additional -mabi with -march (instead of -march implying
a matching abi)?
next prev parent reply other threads:[~2023-05-12 6:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 23:29 juzhe.zhong
2023-05-12 1:03 ` juzhe.zhong
2023-05-12 2:13 ` Kito Cheng
2023-05-12 6:34 ` Robin Dapp [this message]
2023-05-12 7:02 ` Kito Cheng
2023-05-11 23:29 juzhe.zhong
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=4b6ae646-d2d6-c84b-9d86-3e5ca80b3cbf@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 \
--cc=palmer@rivosinc.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).