https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100067
--- Comment #4 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- (In reply to Christophe Lyon from comment #3) > Unfortunately this is causing many regressions in the GCC testsuite. Sigh! I'm not entirely surprised. I suspect most of this is testisms, though. > > For instance: > --target arm-none-linux-gnueabi > --with-mode arm > --with-cpu cortex-a9 > --with-fpu default > gcc.target/arm/armv8_2-fp16-neon-1.c is compiled with > -mfloat-abi=softfp -march=armv8.2-a+fp16 > > /gcc/testsuite/gcc.target/arm/armv8_2-fp16-neon-1.c: In function > 'test_vceqz_16x4': > /gcc/testsuite/gcc.target/arm/armv8_2-fp16-neon-1.c:139:13: warning: > implicit declaration of function 'vceqz_f16'; did you mean 'vceqq_u16'? > [-Wimplicit-function-declaration] > /gcc/testsuite/gcc.target/arm/armv8_2-fp16-neon-1.c:10:25: note: in > definition of macro 'MSTRCAT' > /gcc/testsuite/gcc.target/arm/armv8_2-fp16-neon-1.c:139:1: note: in > expansion of macro 'VCMP1_TEST' > /gcc/testsuite/gcc.target/arm/armv8_2-fp16-neon-1.c:139:13: error: > incompatible types when returning type 'int' but 'uint16x4_t' was expected > [...] It's not obvious what's happening here. I'll look. > > > --target arm-none-linux-gnueabi > --with-mode arm > --with-cpu cortex-a9 > --with-fpu default > Dejagnu flags: -march=armv5t > gcc.target/arm/aes-fuse-1.c is compiled with > > -march=armv5t -mfpu=crypto-neon-fp-armv8 -mfloat-abi=softfp -mcpu=cortex-a72 > cc1: warning: switch '-mcpu=cortex-a72' conflicts with switch '-march=armv5t' The warning is correct. That's a stupid combination to pass to the compiler (arch=armv5 and cpu=<armv8>). What's less clear is why this wasn't happening before.
