From: Jeff Law <jeffreyalaw@gmail.com>
To: Palmer Dabbelt <palmer@dabbelt.com>, juzhe.zhong@rivai.ai
Cc: Kito Cheng <kito.cheng@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] RISC-V: Add attributes for VSETVL PASS
Date: Mon, 28 Nov 2022 21:49:00 -0700 [thread overview]
Message-ID: <0d2a7894-2540-4eb8-b400-59a5e8408f19@gmail.com> (raw)
In-Reply-To: <mhng-31db283b-1ab0-4e13-a7a6-b81dc442384f@palmer-ri-x1c9a>
On 11/28/22 19:56, Palmer Dabbelt wrote:
> On Mon, 28 Nov 2022 17:46:16 PST (-0800), juzhe.zhong@rivai.ai wrote:
>> Yeah, I personally want to support RVV intrinsics in GCC13. As RVV
>> intrinsic is going to release soon next week.
>
> OK, that's fine with me -- I was leaning that way, and I think Jeff only
> had a weak opposition. Are there any more changes required outside the
> RISC-V backend? Those would be the most controversial and are already
> late, but if it's only backend stuff at this point then I'm OK taking
> the risk for a bit longer.
>
> Jeff?
It's not ideal, but I can live with the bits going into gcc-13 as long
as they don't bleed out of the RISC-V port.
Jeff
next prev parent reply other threads:[~2022-11-29 4:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 14:14 juzhe.zhong
2022-11-28 16:44 ` Jeff Law
2022-11-28 18:02 ` Palmer Dabbelt
2022-11-28 23:10 ` 钟居哲
2022-11-28 23:14 ` Palmer Dabbelt
2022-11-28 22:52 ` 钟居哲
2022-11-28 23:54 ` Jeff Law
2022-11-29 1:38 ` Kito Cheng
2022-11-29 1:46 ` juzhe.zhong
2022-11-29 2:56 ` Palmer Dabbelt
2022-11-29 3:07 ` juzhe.zhong
2022-11-29 3:11 ` Palmer Dabbelt
2022-11-29 4:49 ` Jeff Law [this message]
2022-11-29 5:21 ` Palmer Dabbelt
2022-11-29 8:54 ` Kito Cheng
2022-12-01 16:05 ` Kito Cheng
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=0d2a7894-2540-4eb8-b400-59a5e8408f19@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.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).