On Fri, Nov 22, 2024 at 2:40 PM Haochen Jiang <haochen.ji...@intel.com> wrote:
>
> Hi all,
>
> 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.
>
> Tested wieh -march=native with AVX512. Ok for trunk?
Ok.
>
> Thx,
> Haochen
>
> 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(-)
>
> diff --git a/gcc/testsuite/lib/target-supports.exp
> b/gcc/testsuite/lib/target-supports.exp
> index f3828793986..301254afcf5 100644
> --- a/gcc/testsuite/lib/target-supports.exp
> +++ b/gcc/testsuite/lib/target-supports.exp
> @@ -10805,7 +10805,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.
> @@ -10820,7 +10820,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.
> --
> 2.31.1
>
--
BR,
Hongtao
