public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "joshua" <cooper.joshua@linux.alibaba.com>
To: "Kito Cheng" <kito.cheng@gmail.com>
Cc: "Jeff Law" <jeffreyalaw@gmail.com>,
	"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
	"gcc-patches" <gcc-patches@gcc.gnu.org>,
	"kito.cheng" <kito.cheng@sifive.com>,
	"Robin Dapp" <rdapp.gcc@gmail.com>,
	"jkridner" <jkridner@beagleboard.org>,
	"philipp.tomsich" <philipp.tomsich@vrull.eu>
Subject: 回复:RISC-V: Support XTheadVector extensions
Date: Thu, 30 Nov 2023 20:01:10 +0800	[thread overview]
Message-ID: <1feffd40-8bf2-480e-9851-703e12ac3220.cooper.joshua@linux.alibaba.com> (raw)
In-Reply-To: <CA+yXCZA2rh0G5LeX=TZ99brC7Droi9mc53fsYHF1nzmwqpvi9g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1916 bytes --]

Hi Kito,
Thank you for your support. We will get involved into community work actively for our XTheadVector patches. Let's work on upstream together during this process.
Currently, we are polishing up our patches according to Ju-Zhe's suggestions. Patch v3 with higher quality and less invasion will come soon. 
Joshua
------------------------------------------------------------------
发件人:Kito Cheng <kito.cheng@gmail.com>
发送时间:2023年11月18日(星期六) 18:33
收件人:Philipp Tomsich<philipp.tomsich@vrull.eu>
抄 送:Jeff Law<jeffreyalaw@gmail.com>; "juzhe.zhong@rivai.ai"<juzhe.zhong@rivai.ai>; "gcc-patches"<gcc-patches@gcc.gnu.org>; "kito.cheng"<kito.cheng@sifive.com>; "cooper.joshua"<cooper.joshua@linux.alibaba.com>; Robin Dapp<rdapp.gcc@gmail.com>; jkridner<jkridner@beagleboard.org>
主 题:Re: RISC-V: Support XTheadVector extensions
I guess it would be worth to state my thought publicly:
I *support* adding the T-head vector (a.k.a. vector 0.7) to upstream
GCC since T-Head vector already ships a large enough number of boards,
also it's not really T-head's problem as Palmer described in another
mail.
My biggest concern before is T-head folks didn't involved into
community work too much, so accept that definitely will increasing
work for maintainers, however I saw T-head folks is trying to
contribute stuffs to upstream now, so may not a concern now, also I
believe accept this patch will encourage they work more on upstream
together, which is benefit to each other.
Back to the one of the biggest issues for the patch set: GCC 14 or GCC
15. My general thought is it may be OK if it's less invasive enough,
then should be OK for GCC 14, but I don't have a strong opinion, since
as you know I am not the main developer of the vector part, so I will
let Ju-Zhe make the final decision, because he is the one who
contributes most things to RISC-V vector gcc support.

  parent reply	other threads:[~2023-11-30 12:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 11:39 RISC-V: " juzhe.zhong
2023-11-17 16:47 ` Jeff Law
2023-11-18  9:45   ` Philipp Tomsich
2023-11-18 10:32     ` Kito Cheng
2023-11-18 15:16       ` 钟居哲
2023-11-20  3:04       ` juzhe.zhong
2023-11-20 16:58         ` Jason Kridner
2023-11-30 12:01       ` joshua [this message]
2023-11-17 17:11 ` Palmer Dabbelt
2023-11-17 23:16   ` 钟居哲
2023-11-18  0:01     ` Jeff Law
2023-11-18  0:04       ` 钟居哲
2023-11-28 19:45       ` Palmer Dabbelt
2023-11-28 22:14         ` Jeff Law
2023-11-18  9:11 ` Christoph Müllner

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=1feffd40-8bf2-480e-9851-703e12ac3220.cooper.joshua@linux.alibaba.com \
    --to=cooper.joshua@linux.alibaba.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=jkridner@beagleboard.org \
    --cc=juzhe.zhong@rivai.ai \
    --cc=kito.cheng@gmail.com \
    --cc=kito.cheng@sifive.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=rdapp.gcc@gmail.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).