On Wed, Mar 2, 2016 at 1:33 PM, Andre Vieira (lists) <andre.simoesdiasvie...@arm.com> wrote: > On 21/05/15 10:01, Kyrill Tkachov wrote: >> Hi Sandra, >> >> On 21/05/15 06:43, Sandra Loosemore wrote: >>> This is another patch aimed at fixing bugs relating to trying to execute >>> NEON code on a target that doesn't support it revealed by my >>> arm-none-eabi testing on a gazillion different multilibs. Inspired by >>> what vect.exp does and my other patch in this group to fix >>> advsimd-intrinsics.exp, I've hacked simd.exp to test for NEON >>> compilation and execution support and use set dg-do-what-default to >>> either "compile" or "run" as appropriate, or skip the whole set of tests >>> if neither is present. And, I've removed the explicit "dg-do run" and >>> arm_neon_ok test (which only tests for compilation support, not >>> execution support) from all the individual test cases. >>> >>> OK to commit? >> >> This is ok and there is one less headache with NEON testing :) >> Thanks, >> Kyrill >> >>> >>> -Sandra >>> >> > Could we have this backported to the gcc-5-branch? The patch seems to > apply cleanly and it would clean up testing for simd/neon for gcc-5.
OK. Ramana > > Cheers, > Andre
