https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96375
Bug ID: 96375
Summary: [11 regression] arm/lob[2-5].c fail on some
configurations
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
Hi,
Since these new tests were introduced, I've noticed that they fail on some
configurations.
For instance, with target arm-none-linux-gnueabi --with-mode arm --with-cpu
cortex-a9:
spawn -ignore SIGHUP
/aci-gcc-fsf/builds/gcc-fsf-gccsrc/obj-arm-none-linux-gnueabi/gcc3/gcc/xgcc
-B/aci-gcc-fsf/builds/gcc-fsf-gccsrc/obj-arm-none-linux-gnueabi/gcc3/gcc/
/gcc/testsuite/gcc.target/arm/lob2.c -fno-diagnostics-show-caret
-fno-diagnostics-show-line-numbers -fdiagnostics-color=never
-fdiagnostics-urls=never -march=armv8.1-m.main -O3 --save-temps
-ffat-lto-objects -fno-ident -S -o lob2.s
cc1: error: target CPU does not support ARM mode
compiler exited with status 1
FAIL: gcc.target/arm/lob2.c (test for excess errors)
Excess errors:
cc1: error: target CPU does not support ARM mode
gcc.target/arm/lob2.c: output file does not exist
The current dg-skip-if is not sufficient.
Note that lob1.c is UNSUPPORTED in this case, because arm_v8_1_lob_hw_available
fails to compile:
cc1: error: target CPU does not support ARM mode
You probably want to make sure that -mthumb is also used when compiling these
tests.
Sadly, all these new tests are skipped in all my arm-eabi configurations
because I always override -mcpu :-(
