From: Kito Cheng <kito.cheng@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Michael Collison <collison@rivosinc.com>,
juzhe.zhong@rivai.ai, gcc-patches <gcc-patches@gcc.gnu.org>,
"kito.cheng" <kito.cheng@sifive.com>,
"richard.sandiford" <richard.sandiford@arm.com>,
"richard.guenther" <richard.guenther@gmail.com>
Subject: Re: [PATCH] vect: Check that vector factor is a compile-time constant
Date: Fri, 24 Feb 2023 12:04:18 +0800 [thread overview]
Message-ID: <CA+yXCZDiPh7+MMcNTiRUfKAQJidObE7xv=OZ70oqND17r0V-Fg@mail.gmail.com> (raw)
In-Reply-To: <aec8d784-5b57-8d8d-5f27-324d509f0dfc@gmail.com>
Hi Jeff:
> What I'd been planning to do internally at Ventana was to update our
> codebase to gcc-13 once it's released. Then I'd backport RVV autovec
> work from the gcc-14 dev tree into that Ventana branch.
>
> Instead, but along the same lines, we could have a public gcc-13 based
> branch which follows that same process and where Rivos, SiFive, Rivai,
> Ventana (and potentially others with an interest in this space) could
> collaborate. Essentially it'd be gcc-13 + RVV autovec support. We'd
> probably have to hash out a bit of policy with the shared branch, but
> I'd like to think we could make it work.
+1, I like the idea, I could imagine we definitely will do the same
work more than four times by different companies if we don't have a
collaboration branch...
>
> Thoughts?
>
> jeff
>
next prev parent reply other threads:[~2023-02-24 4:04 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 [this message]
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
-- 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='CA+yXCZDiPh7+MMcNTiRUfKAQJidObE7xv=OZ70oqND17r0V-Fg@mail.gmail.com' \
--to=kito.cheng@gmail.com \
--cc=collison@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@sifive.com \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@arm.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).