------- Additional Comments From flash at pobox dot com 2005-07-22 16:04
-------
Looking for a string pattern in the output leaves you vulnerable to
correctly-rejected files which
happen to generate that pattern in an error message. That's probably less of
an issue with GCC's hand-
crafted test code, but it was a real problem with the PalmSource compiler
(which admittedly has more
verbose error reporting) when doing random crash-testing. Our compiler prints
the line it's
complaining about, so a comment about an internal error could give a false
positive. GCC may not have
that problem, but it might still get fooled by a file name.
More generally, unless you know all the possible error strings, you might
miss an error. So I also
looked for the absence of the normal correct-rejection strings, which is also
subject to false positives,
until you get them all. OTOH, if you know that returning with exit code 1
actually means a normal
rejection, then you don't get annoyed with tricky stuff like (in our case, at
least) files named after error
signals.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22600
