From 832e963a477268e023b0fae4e8c59d29be8e7f42 Mon Sep 17 00:00:00 2001 From: Haochen Jiang Date: Fri, 22 Nov 2024 14:32:16 +0800 Subject: i386/testsuite: Do not append AVX10.2 option for check_effective_target When -avx10.2 meet -march with AVX512 enabled, it will report warning for vector size conflict. The warning will prevent the test to run on GCC with arch native build on those platforms when check_effective_target. Remove AVX10.2 options since we are using inline asm ad it actually do not need options. It will eliminate the warning. gcc/testsuite/ChangeLog: * lib/target-supports.exp (check_effective_target_avx10_2): Remove AVX10.2 option. (check_effective_target_avx10_2_512): Ditto. --- gcc/testsuite/lib/target-supports.exp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'gcc') diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp index 187a7e2..b8ac76d 100644 --- a/gcc/testsuite/lib/target-supports.exp +++ b/gcc/testsuite/lib/target-supports.exp @@ -10808,7 +10808,7 @@ proc check_effective_target_avx10_2 { } { __asm__ volatile ("vcvtph2ibs\t%ymm5, %ymm6"); __asm__ volatile ("vminmaxpd\t$123, %ymm4, %ymm5, %ymm6"); } - } "-mavx10.2" ] + } "" ] } # Return 1 if avx10.2-512 instructions can be compiled. @@ -10823,7 +10823,7 @@ proc check_effective_target_avx10_2_512 { } { __asm__ volatile ("vcvtph2ibs\t%zmm5, %zmm6"); __asm__ volatile ("vminmaxpd\t$123, %zmm4, %zmm5, %zmm6"); } - } "-mavx10.2-512" ] + } "" ] } # Return 1 if amx-avx512 instructions can be compiled. -- cgit v1.1