Hi Tamar,
> This testcase on x86_64 needs AVX512 to vectorize.
> My original testing used -march=native so it was on by default.
>
> Tested on aarch64-none-linux-gnu and 86_64-pc-linux-gnu
> -m64 and no issues.
>
> Pushed.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.dg/vect/vect-early-break-no-epilog_11.c: Add AVX512 for x86_64.
>
> ---
>
> diff --git a/gcc/testsuite/gcc.dg/vect/vect-early-break-no-epilog_11.c
> b/gcc/testsuite/gcc.dg/vect/vect-early-break-no-epilog_11.c
> index
> 3a6b72fa5acb1aec9a3bcab5e05e0a28f12c2654..c62727377d24367df08aa41fff4af94ab6cd2f02
> 100644
> --- a/gcc/testsuite/gcc.dg/vect/vect-early-break-no-epilog_11.c
> +++ b/gcc/testsuite/gcc.dg/vect/vect-early-break-no-epilog_11.c
> @@ -3,6 +3,9 @@
> /* { dg-require-effective-target vect_early_break_hw } */
> /* { dg-require-effective-target vect_long } */
>
> +/* { dg-additional-options "-mavx512f" { target { i?86-*-* x86_64-*-* } } }
> */
> +/* { dg-require-effective-target avx512f_hw { target i?86-*-* x86_64-*-* } }
> */
this cannot have been tested at all:
ERROR: gcc.dg/vect/vect-early-break-no-epilog_11.c -flto -ffat-lto-objects:
unknown effective target keyword \`avx512f_hw' for "
dg-require-effective-target 7 avx512f_hw { target i?86-*-* x86_64-*-* } "
avx512f_hw isn't an effective-target keyword: there's no
check_effective_target_avx512f_hw in target-supports.exp, just
check_avx512f_hw_available. I suppose you mean avx512f_runtime instead?
Besides, please use target x86 instead of target { i?86-*-* x86_64-*-* }:
it's shorter and clearer.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
