public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "thenlich at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/47394] New: Internal compiler error when error count limit is reached Date: Fri, 21 Jan 2011 12:46:00 -0000 [thread overview] Message-ID: <bug-47394-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47394 Summary: Internal compiler error when error count limit is reached Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: thenlich@users.sourceforge.net When compiling a program with -fmax-errors=n and the n-th error is encountered, an internal compiler error occurs and the gfortran command exits with status 4. Expected result is: the compiler should report the abortion and exit with the status code according to the error encountered, like the C compiler does. Example: $ echo x > test.f $ gfortran -fmax-errors=1 test.f test.f:1.1: x 1 Error: Non-numeric character in statement label at (1) Fatal Error: Error count reached limit of 1. gfortran.exe: internal compiler error: Aborted (program f951) Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. $ echo $? 4
next reply other threads:[~2011-01-21 12:30 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-21 12:46 thenlich at users dot sourceforge.net [this message] 2011-01-21 13:42 ` [Bug fortran/47394] " burnus at gcc dot gnu.org 2011-01-21 21:45 ` burnus at gcc dot gnu.org 2011-01-21 22:55 ` burnus at gcc dot gnu.org 2011-01-21 22:56 ` burnus at gcc dot gnu.org 2011-11-07 22:43 ` fxcoudert at gcc dot gnu.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=bug-47394-4@http.gcc.gnu.org/bugzilla/ \ --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).