This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [testsuite] vect effective targets should use arm_neon_ok
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: "janisjo at codesourcery dot com" <janisjo at codesourcery dot com>
- Cc: Janis Johnson <janis_johnson at mentor dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 19 Sep 2012 09:43:59 +0100
- Subject: Re: [testsuite] vect effective targets should use arm_neon_ok
- References: <5058D171.9020901@mentor.com> <5058E097.1040300@mentor.com>
On 18/09/12 21:59, Janis Johnson wrote:
> On 09/18/2012 12:54 PM, Janis Johnson wrote:
>> In most cases a test that requires ARM NEON should use effective target
>> arm_neon, which means that flags run for all tests include NEON support.
>> The result is cached the first time it is checked for a multilib.
>>
>> Vectorization tests, when run for ARM, add flags to support NEON if it's
>> OK to do so, but those flags are not reflected in the cached results for
>> arm_neon, nor should they be. Because of this, vect effective-target
>> checks should use arm_neon_ok (as most already do) instead of arm_neon.
>>
>> This patch changes the checks for 7 effective targets, allowing more
>> tests to run and decreasing the number of failures. The only new
>> failures I've seen in tests on arm-none-eabi with a variety of test
>> multilibs are for big-endian with vect_multiple_sizes, which means
>> that vect_multiple_sizes should be false for big endian or that there's
>> a bug in ARM big-endian support.
>
Sadly, there are almost certainly bugs in the big-endian support for ARM
Neon.