public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus 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, 26 Mar 2013 16:58:00 -0000	[thread overview]
Message-ID: <bug-56743-4-ndj3eCv93M@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56743-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-03-26 16:57:53 UTC ---
Created attachment 29734
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29734
Draft patch (only for read_integer)

Draft patch - fixes the issue of the test case, but one probably should do an
audit of the whole file (list_read). For instance, using REAL instead of
INTEGER in the test case also fails. One probably does not need to handle all
CASE_SEPARATORS, but presumably a large number of those.


  parent reply	other threads:[~2013-03-26 16:58 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 [this message]
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
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-ndj3eCv93M@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).