On 24/10/2024 09:50, Torbjörn SVENSSON wrote:
> Ok for trunk and releases/gcc-14?
>
> --
>
> As these tests are set to execute and require neon hardware to do so,
> add the missing dg-require-effective-target arm_neon_hw.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/arm/memset-inline-4.c: Use effective-target
> arm_neon_hw.
> * gcc.target/arm/memset-inline-5.c: Likewise.
> * gcc.target/arm/memset-inline-6.c: Likewise.
>
> Signed-off-by: Torbjörn SVENSSON <torbjorn.svens...@foss.st.com>
These tests combine both a scan-assembler and a run. Unconditionally requiring
neon hardware before running the test means we lose the scan-assembler when the
hardware is not available. But I think you can write
/* { dg-do run { arm_neon_hw } } */
instead and now the framework will only try to run the test if hardware is
available, but will fall back to a compile test otherwise.
Would you mind testing that out, please?
R.
