The current set of flags used in this test cause issues with multilib
testing where there is no neon vs neon support. Thereby adding neon
specific flags through the proper interfaces.
Applied to trunk after testing on arm-none-eabi with a multilib target
list of {-marm/-march=armv7-a/-mfpu=vfpv3-d16/-mfloat-abi=softfp} and
{-mthumb/-march=armv8-a/-mfpu=crypto-neon-fp-armv8/-mfloat-abi=hard} on
the AEM.
Ramana
2014-06-25 Ramana Radhakrishnan <ramana.radhakrish...@arm.com>
* gcc.target/arm/vect-noalign.c: Adjust options.
Index: gcc/testsuite/gcc.target/arm/vect-noalign.c
===================================================================
--- gcc/testsuite/gcc.target/arm/vect-noalign.c (revision 211968)
+++ gcc/testsuite/gcc.target/arm/vect-noalign.c (working copy)
@@ -1,6 +1,7 @@
/* { dg-do run } */
/* { dg-require-effective-target arm_neon_hw } */
-/* { dg-options "-mfpu=neon -ffast-math -ftree-vectorize -fno-common -O2
-mno-unaligned-access" } */
+/* { dg-options "-O2 -fno-common -ftree-vectorize -mno-unaligned-access" } */
+/* { dg-add-options arm_neon } */
/* Test for-mno-unaligned-access and -ftree-vectorize and results bus error.
*/
