public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56743] Namelist bug with comment and no blank
Date: Tue, 21 Apr 2015 16:14:00 -0000 [thread overview]
Message-ID: <bug-56743-4-ktRIk2vfLg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56743-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56743
--- Comment #8 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Author: jvdelisle
Date: Tue Apr 21 16:13:54 2015
New Revision: 222271
URL: https://gcc.gnu.org/viewcvs?rev=222271&root=gcc&view=rev
Log:
2015-04-21 Jerry DeLisle <jvdelisle@gcc.gnu.org>
PR libgfortran/56743
* io/list_read.c (CASE_SEPARATORS): Add case for '!'.
(is_separator): Add condition for '!'.
(eat_separator): Use notify_std to warn or errord if '!' is
encountered before a proper separator.
Modified:
trunk/libgfortran/ChangeLog
trunk/libgfortran/io/list_read.c
next prev parent reply other threads:[~2015-04-21 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 16:20 [Bug fortran/56743] New: " janus at gcc dot gnu.org
2013-03-26 16:27 ` [Bug fortran/56743] " dominiq at lps dot ens.fr
2013-03-26 16:58 ` burnus at gcc dot gnu.org
2013-03-30 4:08 ` jvdelisle at gcc dot gnu.org
2013-03-30 10:47 ` burnus at gcc dot gnu.org
2013-05-03 20:32 ` jvdelisle at gcc dot gnu.org
2015-04-07 19:28 ` jvdelisle at gcc dot gnu.org
2015-04-16 2:23 ` jvdelisle at gcc dot gnu.org
2015-04-21 16:14 ` jvdelisle at gcc dot gnu.org [this message]
2015-04-21 16:34 ` jvdelisle at gcc dot gnu.org
2015-04-21 16:42 ` jvdelisle 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-56743-4-ktRIk2vfLg@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).