On 04/11/2024 20:14, Torbjorn SVENSSON wrote:
>
>
> On 2024-11-04 16:47, Richard Earnshaw (lists) wrote:
>> On 20/10/2024 16:51, Torbjörn SVENSSON wrote:
>>> Ok for trunk and releases/gcc-14?
>>>
>>> --
>>>
>>> The tests assume that a neon fpu is avialable and fails it not, so
>>> explicitly req
On 2024-11-04 16:47, Richard Earnshaw (lists) wrote:
On 20/10/2024 16:51, Torbjörn SVENSSON wrote:
Ok for trunk and releases/gcc-14?
--
The tests assume that a neon fpu is avialable and fails it not, so
explicitly require it.
diff --git a/gcc/testsuite/gcc.target/arm/attr-neon2.c
b/gcc/
On 20/10/2024 16:51, Torbjörn SVENSSON wrote:
> Ok for trunk and releases/gcc-14?
>
> --
>
> The tests assume that a neon fpu is avialable and fails it not, so
> explicitly require it.
> diff --git a/gcc/testsuite/gcc.target/arm/attr-neon2.c
> b/gcc/testsuite/gcc.target/arm/attr-neon2.c
> index
Ok for trunk and releases/gcc-14?
--
The tests assume that a neon fpu is avialable and fails it not, so
explicitly require it.
gcc/testsuite/ChangeLog:
* gcc.target/arm/attr-neon-builtin-fail.c: Use effective-target
arm_neon.
* gcc.target/arm/attr-neon-builtin-fail2.c: L