On Tue, 8 Apr 2025 14:27:16 -0600, Jeff Law wrote: > > > On 4/7/25 12:26 AM, Jin Ma wrote: > > XThreadVector does not support the vsext/vzext instructions; however, > > due to the reuse of RVV optimizations, it may generate these instructions > > in certain cases. To prevent the error "Unknown opcode 'th.vsext.vf2'," > > we should disable these patterns. > > > > V2: > > Change the value of dg-do in the test case from assemble to compile, and > > remove the -save-temps option. > > > > gcc/ChangeLog: > > > > * config/riscv/vector.md: Disable vsext/vzext for XTheadVector. > > > > gcc/testsuite/ChangeLog: > > > > * gcc.target/riscv/rvv/xtheadvector/vsext.c: New test. > > * gcc.target/riscv/rvv/xtheadvector/vzext.c: New test. > OK for the trunk. Thanks! > > Also OK if you wanted to backport to gcc-14.
Thank you very much! After conducting thorough testing locally, I will attempt to cherry-pick them into the gcc-14 branch. By the way, do we have a pre-commit CI system in place for the gcc-14 branch similar to that of the trunk branch? If so, how can I trigger it and monitor the status of the patches in the CI system? Best regards, Jin Ma
