> Shouldn't all these (in the file) be vsext_vf? Copy-paste issue, will fix it in v2.
Pan -----Original Message----- From: Robin Dapp <[email protected]> Sent: Friday, July 3, 2026 5:31 PM To: Li, Pan2 <[email protected]>; [email protected] Cc: [email protected]; [email protected]; [email protected]; [email protected]; Chen, Ken <[email protected]>; Liu, Hongtao <[email protected]> Subject: Re: [PATCH v1 2/3] RISC-V: Add test cases for vsext.vf2 reg overlap > +/* { dg-do compile } */ > +/* { dg-options "-march=rv64gcv -mabi=lp64d" } */ > + > +#include "group_overlap.h" > + > +DEF_GROUP_OVERLAP_UNARY_0( > + __riscv_vsetvlmax_e16m1, > + vint16m1_t, > + vint32m2_t, > + __riscv_vle16_v_i16m1, > + __riscv_vsext_vf2_i32m2, > + __riscv_vse32_v_i32m2, > + vzext_vf, Shouldn't all these (in the file) be vsext_vf? -- Regards Robin
