public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/61049] [4.9/4.10 Regression] NIST test FM906 fails
Date: Mon, 05 May 2014 09:16:00 -0000	[thread overview]
Message-ID: <bug-61049-4-AfsXTe5Z4f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61049-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
The following patch also fixes this PR (regtested and NIST suite)

--- ../_clean/libgfortran/io/list_read.c    2014-04-27 00:39:19.000000000 +0200
+++ libgfortran/io/list_read.c    2014-05-05 09:53:52.000000000 +0200
@@ -2066,6 +2066,7 @@ list_formatted_read_scalar (st_parameter
           && dtp->u.p.current_unit->decimal_status == DECIMAL_POINT))
         {
           dtp->u.p.comma_flag = 1;
+          eat_separator (dtp);
           goto cleanup;
         }


I have no opinion about which patch is better, i.e., I don't have any test
which succeeds with one patch, but fails with the other.


  parent reply	other threads:[~2014-05-05  9:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-03 21:00 [Bug libfortran/61049] New: " dominiq at lps dot ens.fr
2014-05-03 23:22 ` [Bug libfortran/61049] " jvdelisle at gcc dot gnu.org
2014-05-04 11:05 ` dominiq at lps dot ens.fr
2014-05-05  0:10 ` jvdelisle at gcc dot gnu.org
2014-05-05  0:11 ` jvdelisle at gcc dot gnu.org
2014-05-05  9:13 ` rguenth at gcc dot gnu.org
2014-05-05  9:16 ` dominiq at lps dot ens.fr [this message]
2014-05-07  1:32 ` jvdelisle at gcc dot gnu.org
2014-05-07  1:46 ` jvdelisle at gcc dot gnu.org
2014-05-11  3:48 ` jvdelisle at gcc dot gnu.org
2014-05-11  3:53 ` jvdelisle at gcc dot gnu.org
2014-05-11  4:33 ` 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-61049-4-AfsXTe5Z4f@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).