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.ch...@gmail.com>
发送时间：2023年11月18日(星期六) 18:33
收件人：Philipp Tomsich<philipp.toms...@vrull.eu>
抄 送：Jeff Law<jeffreya...@gmail.com>;
"juzhe.zh...@rivai.ai"<juzhe.zh...@rivai.ai>;
"gcc-patches"<gcc-patches@gcc.gnu.org>; "kito.cheng"<kito.ch...@sifive.com>;
"cooper.joshua"<cooper.jos...@linux.alibaba.com>; Robin
Dapp<rdapp....@gmail.com>; jkridner<jkrid...@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.
