https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100067
Christophe Lyon <clyon at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clyon at gcc dot gnu.org --- Comment #3 from Christophe Lyon <clyon at gcc dot gnu.org> --- Unfortunately this is causing many regressions in the GCC testsuite. 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 [...] --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' FAIL: gcc.target/arm/aes-fuse-1.c (test for excess errors) For a full picture of the regressions I noticed: https://people.linaro.org/~christophe.lyon/cross-validation/gcc/trunk/r11-8168-gd1e4368ddb76a92c44f824c8e4ca1a3de8149342/report-build-info.html (click on "log" to download the corresponding gcc.log and see the error messages) (you can ignore the regressions in g++, they are caused by a previous commit)