Currently I start to work on full coverage testing (with different compile option test GCC testsuite) and fix bugs which is highest priority definitely.
I am not able to find the time review this patch on GCC-14 for now. So conservatively, postpone it to GCC-15. If we are lucky that I stablize RVV support quickly, we still have a chance to make it landed on GCC-14. It all depends on my review. But no worry, I will review that eventually. juzhe.zh...@rivai.ai From: Kito Cheng Date: 2023-11-18 18:32 To: Philipp Tomsich CC: Jeff Law; juzhe.zh...@rivai.ai; gcc-patches; kito.cheng; cooper.joshua; Robin Dapp; jkridner Subject: 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.
