public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldot at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/23538] gfortran hangs on old cray fortran 66 program Date: Mon, 06 Nov 2006 19:15:00 -0000 [thread overview] Message-ID: <20061106191456.22536.qmail@sourceware.org> (raw) In-Reply-To: <bug-23538-10129@http.gcc.gnu.org/bugzilla/> ------- Comment #10 from aldot at gcc dot gnu dot org 2006-11-06 19:14 ------- Should there be a default (I currently default to 100) for -ferror-count? I did choose to add one single check into gfc_warning_check, so we don't immediately bail out if the error count did exceed the given limit. Is this enough or is it better to instrument all of the error code to instantaneously bail if the limit is reached? For the testcase, trunk currently ICE like so, fwiw: Error: END DO statement expected at (1) d2ds.f:1718: subroutine stravg 1 Error: Unclassifiable statement at (1) Program received signal SIGSEGV, Segmentation fault. 0x0000000000442fd4 in gfc_match_common () at ../../../src/gcc-4.3/gcc/fortran/match.c:2349 2349 while (tail->common_next) (gdb) bt #0 0x0000000000442fd4 in gfc_match_common () at ../../../src/gcc-4.3/gcc/fortran/match.c:2349 #1 0x000000000044ecc0 in match_word (str=0xa47600 "common", subr=0x442e26 <gfc_match_common>, old_locus=0x7fffffd75220) at ../../../src/gcc-4.3/gcc/fortran/parse.c:65 #2 0x000000000044f164 in decode_statement () at ../../../src/gcc-4.3/gcc/fortran/parse.c:193 #3 0x00000000004502ef in next_fixed () -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23538
next prev parent reply other threads:[~2006-11-06 19:15 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23538-10129@http.gcc.gnu.org/bugzilla/> 2005-11-02 21:18 ` tkoenig at gcc dot gnu dot org 2006-01-10 2:46 ` pinskia at gcc dot gnu dot org 2006-06-04 10:19 ` fxcoudert at gcc dot gnu dot org 2006-11-06 19:15 ` aldot at gcc dot gnu dot org [this message] 2006-11-06 19:41 ` aldot at gcc dot gnu dot org 2006-11-10 17:35 ` aldot at gcc dot gnu dot org 2007-03-05 18:57 ` brooks at gcc dot gnu dot org 2007-03-05 20:20 ` brooks at gcc dot gnu dot org 2007-03-09 22:22 ` brooks at gcc dot gnu dot org 2005-08-23 21:03 [Bug fortran/23538] New: " dir at lanl dot gov 2005-08-23 21:18 ` [Bug fortran/23538] " dir at lanl dot gov 2005-08-23 21:22 ` kargl at gcc dot gnu dot org 2005-08-23 21:45 ` kargl at gcc dot gnu dot org 2005-08-24 13:51 ` dir at lanl dot gov 2005-08-24 18:05 ` kargl at gcc dot gnu dot org 2005-08-24 20:51 ` dir at lanl dot gov
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=20061106191456.22536.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).