http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54139

             Bug #: 54139
           Summary: [4.8 regression] some ARM Thumb-2 tests appear to be
                    run on ARMv5TE hardware causing unhandled exceptions
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
        AssignedTo: unassig...@gcc.gnu.org
        ReportedBy: mi...@it.uu.se


Bootstrapping gcc-4.8 on armv5tel-linux-gnueabi and running the test suite now
results in kernel messages about unhandled exceptions from (what appears to be)
Thumb-2 specific test cases:

Alignment trap: ftest-armv6t2-t (1910) PC=0x0000842e Instr=0x3304601a
Address=0x00008501 FSR 0x801
Alignment trap: not handling instruction 3304601a at [<0000842e>]
Unhandled fault: alignment exception (0x801) at 0x00008501
Alignment trap: ftest-armv7a-th (1982) PC=0x0000842e Instr=0x3304601a
Address=0x00008509 FSR 0x801
Alignment trap: not handling instruction 3304601a at [<0000842e>]
Unhandled fault: alignment exception (0x801) at 0x00008509
Alignment trap: ftest-armv7r-th (2042) PC=0x0000842e Instr=0x3304601a
Address=0x00008509 FSR 0x801
Alignment trap: not handling instruction 3304601a at [<0000842e>]
Unhandled fault: alignment exception (0x801) at 0x00008509

The program names are truncated, but clearly correspond to
ftest-armv6t2-thumb.c, ftest-armv7a-thumb.c, and ftest-armv7r-thumb.c in
gcc/testsuite/gcc.target/arm/.

This seems to have started some time between 20120624 and 20120701.  The test
suite results between those two dates show:

+FAIL: gcc.target/arm/ftest-armv6t2-thumb.c execution test
+FAIL: gcc.target/arm/ftest-armv7a-thumb.c execution test
+FAIL: gcc.target/arm/ftest-armv7r-thumb.c execution test

As the same time ARM's mmx-2.c test case started failing at compile-time:

+FAIL: gcc.target/arm/mmx-2.c (test for excess errors)

and a look in the detailed log show 100+ lines of warnings and errors related
to numerous __builtin_arm_${foo} not being recognized.

Reply via email to