If one forces -marm in RUNTESTFLAGS, we end up compiling this test with
-marm [...] -mfpu=auto -march=armv8.1-m.main+mve [...]
leading to a failure error: target CPU does not support ARM mode
Add -mthumb to dg-options to avoid this problem.
gcc/testsuite/ChangeLog:
* gcc.target/arm/mve/general-c/nomve_fp_1.c: Add -mthumb to
dg-options.
---
gcc/testsuite/gcc.target/arm/mve/general-c/nomve_fp_1.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/testsuite/gcc.target/arm/mve/general-c/nomve_fp_1.c
b/gcc/testsuite/gcc.target/arm/mve/general-c/nomve_fp_1.c
index c9d279ead68..1a18b3d2038 100644
--- a/gcc/testsuite/gcc.target/arm/mve/general-c/nomve_fp_1.c
+++ b/gcc/testsuite/gcc.target/arm/mve/general-c/nomve_fp_1.c
@@ -4,7 +4,7 @@
/* Do not use dg-add-options arm_v8_1m_mve, because this might expand to "",
which could imply mve+fp depending on the user settings. We want to make
sure the '+fp' extension is not enabled. */
-/* { dg-options "-mfpu=auto -march=armv8.1-m.main+mve" } */
+/* { dg-options "-mfpu=auto -march=armv8.1-m.main+mve -mthumb" } */
/* { dg-add-options arm_fp } */
#include <arm_mve.h>
--
2.43.0
