Hi Ezra, > On 9 Jul 2026, at 14:40, [email protected] <[email protected]> wrote: > > From: Ezra Sitorus <[email protected]> > > gcc/testsuite/ChangeLog: > * lib/target-supports.exp (exts): Add "sve2p1", "sve2p2", > "sve2p3" and "sme2p3" > --- > gcc/testsuite/lib/target-supports.exp | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/gcc/testsuite/lib/target-supports.exp > b/gcc/testsuite/lib/target-supports.exp > index cab72c8a9e10..030d158b9050 100644 > --- a/gcc/testsuite/lib/target-supports.exp > +++ b/gcc/testsuite/lib/target-supports.exp > @@ -12909,10 +12909,11 @@ proc > check_effective_target_aarch64_gas_has_dtprel_reloc { } { > set exts { > "bf16" "cmpbr" "crc" "crypto" "dotprod" "f32mm" "f64mm" "faminmax" > "fp" "fp8" "fp8dot2" "fp8dot4" "fp8fma" "i8mm" "ls64" "lse" "lut" > - "sb" "simd" "sve-b16b16" "sve" "sve2" "sve-sm4" "sve-aes" "sve-bitperm" > + "sb" "simd" "sve-b16b16" "sve" "sve2" "sve2p1" "sve2p2" "sve2p3"
There already check_effective_target_aarch64_asm_sve2p1_ok and check_effective_target_aarch64_asm_sve2p2_ok routines below, so I don’t think you need to add sve2p1 and sve2p2 here. Ok otherwise. Thanks, Kyrill > + "sve-sm4" "sve-aes" "sve-bitperm" > "sve-sha3" "f8f16mm" "f8f32mm" "sve-f16f32mm" > "sme-f8f16" "sme-f8f32" > - "sme-b16b16" "sme-f16f16" "sme-i16i64" "sme" "sme2" "sme2p1" "sme2p2" > + "sme-b16b16" "sme-f16f16" "sme-i16i64" "sme" "sme2" "sme2p1" "sme2p2" > "sme2p3" > "ssve-fp8dot2" "ssve-fp8dot4" "ssve-fp8fma" "sve-bfscale" "sme-lutv2" > "ssve-fexpa" "ssve-bitperm" "ssve-aes" > } > -- > 2.53.0 >
