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 libfortran/56786] [4.6/4.7/4.8/4.9 Regression] Namelist read fails with designators containing embedded spaces
Date: Mon, 01 Apr 2013 00:05:00 -0000	[thread overview]
Message-ID: <bug-56786-4-903xKVolKf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56786-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #1 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> 2013-04-01 00:05:14 UTC ---
Author: jvdelisle
Date: Sun Mar 31 20:32:33 2013
New Revision: 197290

URL: http://gcc.gnu.org/viewcvs?rev=197290&root=gcc&view=rev
Log:
2013-03-31  Jerry DeLisle  <jvdelisle@gcc.gnu.org>

    PR libfortran/56786
    * io/list_read.c (nml_parse_qualifier): Remove spurious next_char call
    when checking for EOF. Use error return mechanism when EOF detected.
    Do not return false unless parse_err_msg and parse_err_msg_size have
    been set. Use hit_eof.
    (nml_get_obj_data): Likewise use the correct error mechanism.
    * io/transfer.c (hit_eof): Do not set AFTER_ENDFILE if in namelist
    mode.

Modified:
    trunk/libgfortran/ChangeLog
    trunk/libgfortran/io/list_read.c
    trunk/libgfortran/io/transfer.c


  reply	other threads:[~2013-04-01  0:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-30 10:18 [Bug libfortran/56786] New: " burnus at gcc dot gnu.org
2013-04-01  0:05 ` jvdelisle at gcc dot gnu.org [this message]
2013-04-01 20:26 ` [Bug libfortran/56786] " burnus at gcc dot gnu.org
2013-04-01 20:27 ` burnus at gcc dot gnu.org
2013-04-01 20:29 ` burnus at gcc dot gnu.org
2013-04-02  9:08 ` rguenth at gcc dot gnu.org
2013-04-12 15:18 ` [Bug libfortran/56786] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2013-04-27 22:51 ` jvdelisle at gcc dot gnu.org
2013-04-28 16:56 ` jvdelisle at gcc dot gnu.org
2013-04-28 17:21 ` jvdelisle at gcc dot gnu.org
2013-04-28 17:21 ` 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-56786-4-903xKVolKf@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).