public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30779] [4.1, 4.2 only] incomplete file triggers ICE
Date: Fri, 16 Feb 2007 23:42:00 -0000 [thread overview]
Message-ID: <20070216234221.32680.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30779-6642@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from jvdelisle at gcc dot gnu dot org 2007-02-16 23:42 -------
Subject: Bug 30779
Author: jvdelisle
Date: Fri Feb 16 23:42:11 2007
New Revision: 122059
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=122059
Log:
2007-02-16 Jerry DeLisle <jvdelisle@gcc.gnu.org>
PR fortran/30779
* scanner.c (gfc_next_char_literal): Add check for end of file after
call to advance_line.
2007-02-16 Jerry DeLisle <jvdelisle@gcc.gnu.org>
PR fortran/30779
* gfortran.dg/error_recovery_3.f90: New test.
Added:
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/error_recovery_3.f90
Modified:
branches/gcc-4_2-branch/gcc/fortran/ChangeLog
branches/gcc-4_2-branch/gcc/fortran/scanner.c
branches/gcc-4_2-branch/gcc/testsuite/ChangeLog
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30779
next prev parent reply other threads:[~2007-02-16 23:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 19:14 [Bug fortran/30779] New: " jv244 at cam dot ac dot uk
2007-02-12 19:30 ` [Bug fortran/30779] " tkoenig at gcc dot gnu dot org
2007-02-12 20:12 ` jv244 at cam dot ac dot uk
2007-02-13 21:00 ` pault at gcc dot gnu dot org
2007-02-14 0:43 ` jvdelisle at gcc dot gnu dot org
2007-02-14 20:31 ` jvdelisle at gcc dot gnu dot org
2007-02-14 20:54 ` paulthomas2 at wanadoo dot fr
2007-02-15 6:25 ` patchapp at dberlin dot org
2007-02-15 6:48 ` jvdelisle at gcc dot gnu dot org
2007-02-15 6:52 ` jvdelisle at gcc dot gnu dot org
2007-02-15 7:04 ` [Bug fortran/30779] [4.1, 4.2 only] " jvdelisle at gcc dot gnu dot org
2007-02-16 23:42 ` jvdelisle at gcc dot gnu dot org [this message]
2007-02-16 23:52 ` jvdelisle 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=20070216234221.32680.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: 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).