I would prefer this is the branch based on gcc-13 where we backport
autovec-related patches once they've landed on trunk.
I won't do any development on this branch, instead, I would just use it for
releasing my downstream GCC.
I will directly support auto-vectorization on the trunk since the mos
>> I would object to anyone trying to push forward an autovec implementation
>> into
>> gcc-13. We're well past that point IMHO, even if the changes only
>> affected the RISC-V backend.
Yes, I am agree with Jeff's opinion. I finished infrastructure (intrinsic and
VSETVL PASS) of RVV now.
Now, I
Besides, since GCC 13 currently is on stage 4.
Unlike the infrastructure that I am building for intrinsic && auto-vec which is
safe and will not affect the original RISC-V port functionality.
Auto-vectorization will potentially affect the orignal RISC-V port
functionality which is not safe to su
Currently, upstream GCC is not ready to support auto-vec.
I am building the basic infrastructure of RVV and need more testing.
I can't support auto-vec now since it depends on the infrastructure tha I am
building.
I have open source "rvv-next" in RISC-V foundation repo which fully support
intrins
