From: Jeff Law <jeffreyalaw@gmail.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: gcc-patches@gcc.gnu.org, Vineet Gupta <vineetg@rivosinc.com>,
Kito Cheng <kito.cheng@gmail.com>,
collison@rivosinc.com, juzhe.zhong@rivai.ai,
kito.cheng@sifive.com, richard.sandiford@arm.com,
richard.guenther@gmail.com
Subject: Re: [PATCH] vect: Check that vector factor is a compile-time constant
Date: Sat, 25 Mar 2023 16:45:33 -0600 [thread overview]
Message-ID: <08bf03ee-d5aa-fc95-b630-3e3facd373b0@gmail.com> (raw)
In-Reply-To: <mhng-786e5f66-82f6-44bb-9208-56d7eb3a9232@palmer-ri-x1c9a>
On 3/23/23 20:28, Palmer Dabbelt wrote:
> On Thu, 23 Mar 2023 16:18:20 PDT (-0700), jeffreyalaw@gmail.com wrote:
>
> OK. We don't have a hard need there, but it'll make life easier so I'm
> happy to just treat it like a real shipping branch if you guys are going
> to as well.
I'd planned to use it for Ventana's gcc-13 baseline since we're going to
want RVV support before gcc-14 hits the streets. So from Ventana's
viewpoint is's like a real shipping branch.
>
> Are you OK just having a single "gcc-13 with RISC-V performance
> backports" branch, or do you want just vector backports? Our internal
> branch would be all performance-related backports, but no big deal if
> the upstream stuff is vector-only as that's probably going to be 90%+ of
> the churn.
I can live with performance backports. It wasn't my original intent,
but I see the benefits to the ecosystem.
>
>> Thanks for raising the need for a development coordination branch.
>
> I guess "need" is kind of strong: IMO it's up to the people actually
> doing the work how to organize the branches. I'm not writing the code
> here so I'm happy with whatever, just pointing out that there's two
> different things that could be done ;)
I think there's enough interested parties for the development side as
well that ca;ling it a "need" isn't a significant stretch.
jeff
next prev parent reply other threads:[~2023-03-25 22:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 15:27 juzhe.zhong
2023-02-22 17:54 ` Michael Collison
2023-02-22 23:43 ` juzhe.zhong
2023-02-22 23:47 ` juzhe.zhong
2023-02-23 4:01 ` Jeff Law
2023-02-23 4:25 ` juzhe.zhong
2023-02-23 4:50 ` Michael Collison
2023-02-24 3:34 ` Jeff Law
2023-02-24 4:04 ` Kito Cheng
2023-03-14 17:48 ` Jeff Law
2023-03-17 16:57 ` Palmer Dabbelt
2023-03-17 16:57 ` Palmer Dabbelt
2023-03-21 2:02 ` juzhe.zhong
2023-03-23 23:18 ` Jeff Law
2023-03-24 2:28 ` Palmer Dabbelt
2023-03-25 22:45 ` Jeff Law [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-21 23:02 Michael Collison
2023-02-22 8:20 ` Richard Biener
2023-02-22 16:42 ` Michael Collison
2023-02-23 9:08 ` Richard Biener
2023-02-27 14:51 ` Richard Sandiford
2023-03-01 21:00 ` Michael Collison
2023-03-02 7:56 ` Richard Biener
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=08bf03ee-d5aa-fc95-b630-3e3facd373b0@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=collison@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=palmer@rivosinc.com \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@arm.com \
--cc=vineetg@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).