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/35882] Miscounted continuation lines when interspersed with data
Date: Sun, 20 Apr 2008 21:13:00 -0000	[thread overview]
Message-ID: <20080420211218.10838.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35882-15996@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from jvdelisle at gcc dot gnu dot org  2008-04-20 21:12 -------
Subject: Bug 35882

Author: jvdelisle
Date: Sun Apr 20 21:11:22 2008
New Revision: 134493

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=134493
Log:
2008-04-20  Jerry DeLisle  <jvdelisle@gcc.gnu.org>

        PR fortran/35882
        * scanner.c (skip_fixed_comments): Update continue_line when comment is
        detected. (gfc_next_char_literal): Likewise.

        PR fortran/35882
        * gfortran.dg/continuation_5.f: Add some comment lines.
        * gfortran.dg/continuation_3.f90: Add some comment lines.

Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/scanner.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gfortran.dg/continuation_3.f90
    trunk/gcc/testsuite/gfortran.dg/continuation_5.f


-- 


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


      parent reply	other threads:[~2008-04-20 21:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09  8:08 [Bug fortran/35882] New: " J dot Hogg at rl dot ac dot uk
2008-04-09  9:06 ` [Bug fortran/35882] " burnus at gcc dot gnu dot org
2008-04-09  9:19 ` burnus at gcc dot gnu dot org
2008-04-14  0:45 ` jvdelisle at gcc dot gnu dot org
2008-04-14  0:48 ` jvdelisle at gcc dot gnu dot org
2008-04-14  1:14 ` jvdelisle at gcc dot gnu dot org
2008-04-20 21:13 ` jvdelisle at gcc dot gnu dot org [this message]

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=20080420211218.10838.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).