https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100067
--- Comment #5 from Christophe Lyon <clyon at gcc dot gnu.org> --- (In reply to Richard Earnshaw from comment #4) > (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. > :-) Yes, probably. > > --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. Indeed. I just checked the command line was the same before your patch (i.e. your patch has no impact on the effective-targets that could change the flags used) FTR, even before your patch there were several such annoying warnings.