From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Jerry DeLisle <jvdelisle@charter.net>
Cc: gfortran <fortran@gcc.gnu.org>, gcc patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran] [5/6 Regression] Line continuation followed by comment character in string fails to compile
Date: Sat, 16 May 2015 15:17:00 -0000 [thread overview]
Message-ID: <20150516151156.GA89083@troutmask.apl.washington.edu> (raw)
In-Reply-To: <555759B6.1070901@charter.net>
On Sat, May 16, 2015 at 07:52:38AM -0700, Jerry DeLisle wrote:
> * ping *
>
> > 2015-05-14 Jerry DeLisle <jvdelisle@gcc.gnu.org>
> >
> > PR fortran/65903
> > * io.c (format_lex): Change to NONSTRING when checking for
> > possible doubled quote.
> > * scanner.c (gfc_next_char_literal): Revert change from 64506,
> > add a check for quotes, and return.
> >
OK.
--
Steve
next prev parent reply other threads:[~2015-05-16 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 2:18 Jerry DeLisle
2015-05-16 15:09 ` Jerry DeLisle
2015-05-16 15:17 ` Steve Kargl [this message]
2015-05-16 19:00 ` Jerry DeLisle
2015-05-16 20:33 ` Jerry DeLisle
2015-05-17 15:13 ` Jerry DeLisle
2015-05-16 15:54 ` Mikael Morin
2015-05-16 17:45 ` Jerry DeLisle
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=20150516151156.GA89083@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jvdelisle@charter.net \
/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).