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] New: Exit code should be different from 1 for internal compiler error Date: Thu, 21 Jul 2005 22:13:00 -0000 [thread overview] Message-ID: <20050721220749.22600.flash@pobox.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1334 bytes --] Steps: 93> /opt/gcc401chk/bin/g++ -pass-exit-codes ../cpp/bugfiles/error/EckelRob_104822.ii ../jammed/Barney/eckel.cpp:2039: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. 94> echo $? [This uses my file for bug 22508.] Actual Result: 1 Expected Result: Anything but 1 or 0. For recursive crash testing, the return code for an internal compiler error should be distinguishable from that for correct rejection of incorrect code. As a workaround, I've been checking the output for the presence and absence of various patterns, but this is inelegant and subject to error. PalmSource bug 50522. -- Summary: Exit code should be different from 1 for internal compiler error Product: gcc Version: 4.0.1 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: driver AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: flash at pobox dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22600
next reply other threads:[~2005-07-21 22:07 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-21 22:13 flash at pobox dot com [this message] 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 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
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=20050721220749.22600.flash@pobox.com \ --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).