public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "flash at pobox dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/22600] Exit code should be different from 1 for internal compiler error Date: Fri, 22 Jul 2005 16:18:00 -0000 [thread overview] Message-ID: <20050722160404.21214.qmail@sourceware.org> (raw) In-Reply-To: <20050721220749.22600.flash@pobox.com> ------- 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
next prev parent reply other threads:[~2005-07-22 16:04 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-21 22:13 [Bug driver/22600] New: " flash at pobox dot com 2005-07-21 22:14 ` [Bug driver/22600] " pinskia at gcc dot gnu dot org 2005-07-21 22:26 ` pinskia at gcc dot gnu dot org 2005-07-22 14:49 ` reichelt at gcc dot gnu dot org 2005-07-22 16:18 ` flash at pobox dot com [this message] 2005-07-22 16:52 ` pinskia at gcc dot gnu dot org 2005-07-23 5:11 ` flash at pobox dot com 2005-09-08 3:07 ` mmitchel at gcc dot gnu dot org [not found] <bug-22600-8581@http.gcc.gnu.org/bugzilla/> 2006-03-19 21:03 ` patchapp at dberlin dot org 2006-03-22 19:36 ` reichelt at gcc dot gnu dot org 2006-03-22 20:14 ` reichelt at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20050722160404.21214.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).