The testsuite does not check for ICEs. Therefore, ICEs often go unnoticed
when they happen in a line that is marked with { dg-error "" }.
(See e.g. PR 24128, PR 26739, PR 26740 and several others).
Btw, this is somewhat similar to
PR 25241 "DejaGNU does not distinguish between errors and warnings".
With the patch for PR 22600 in place, at least three frontends
(C, C++, Fortran) have different exit codes for ICEs (4) and regular
errors (<4). So this is a first step to be able to identify ICEs in the
testsuite.
There are two remaining problems:
* First, the driver passes the exit status of the frontend only when
the command line option -pass-exit-codes is given.
So we either have to supply this option automagically in the testsuite
or make it the default.
* The second problem is in target_compile.
This function currently does not return the exit status of the compiler,
but a different status.
Well, there's a completely different approach: One can test for ICEs by
inspecting the error messages more closely. But that is more error-prone
than checking the exit status.
--
Summary: Testsuite does not check for ICEs
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: testsuite
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: reichelt at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26813
