public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47394] Internal compiler error when error count limit is reached
Date: Fri, 21 Jan 2011 22:55:00 -0000	[thread overview]
Message-ID: <bug-47394-4-2CLmelqyIM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47394-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47394

--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-01-21 22:38:58 UTC ---
Author: burnus
Date: Fri Jan 21 22:38:55 2011
New Revision: 169109

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=169109
Log:
2011-01-21  Tobias Burnus  <burnus@net-b.de>

        PR fortran/47394
        * error.c (gfc_error_now, gfc_fatal_error, gfc_error_check):
        Use defined instead of magic number exit status codes.
        * scanner.c (include_line, gfc_new_file): Ditto.
        * gfortranspec.c (lang_specific_driver): Ditto.


Modified:
    branches/gcc-4_5-branch/gcc/fortran/ChangeLog
    branches/gcc-4_5-branch/gcc/fortran/error.c
    branches/gcc-4_5-branch/gcc/fortran/gfortranspec.c
    branches/gcc-4_5-branch/gcc/fortran/scanner.c


  parent reply	other threads:[~2011-01-21 22:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 12:46 [Bug fortran/47394] New: " thenlich at users dot sourceforge.net
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 [this message]
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-2CLmelqyIM@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: link
Be 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).