Hmm I'll need to check why this worked for me. Thanks for the fix, Tamar
________________________________ From: H.J. Lu <[email protected]> Sent: Thursday, May 28, 2026 9:35 PM To: Tamar Christina <[email protected]> Cc: GCC Patches <[email protected]>; nd <[email protected]>; Richard Biener <[email protected]>; [email protected] <[email protected]> Subject: [COMMITTED, PATCH] vect-early-break-no-epilog_11.c: Require avx512f_runtime On Thu, May 28, 2026 at 8:38 PM Tamar Christina <[email protected]> wrote: > > 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. Require avx512f_runtime instead of avx512f_hw to fix 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-*-* } " * gcc.dg/vect/vect-early-break-no-epilog_11.c: Require avx512f_runtime instead of avx512f_hw. > 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-*-* } } > */ > + > #include "tree-vect.h" > > __attribute__ ((noipa)) > > > -- -- H.J.
