public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/38097] I/O with blanks in exponent fails; blank="NULL", BN edit descriptor
Date: Sun, 16 Nov 2008 16:15:00 -0000	[thread overview]
Message-ID: <20081116161343.29976.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38097-12362@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from jvdelisle at gcc dot gnu dot org  2008-11-16 16:13 -------
Subject: Bug 38097

Author: jvdelisle
Date: Sun Nov 16 16:12:16 2008
New Revision: 141919

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=141919
Log:
2008-11-16  Jerry DeLisle  <jvdelisle@gcc.gnu.org>

        PR libfortran/38097
        * io/read.c (read_f): Initialize exponent. Fix comment. Set loop
        conditions for BZ/BN.
        * io/unit.c (get_internal_unit): Initialize flags.blank.
        * io/transfer.c (data_transfer_init): Fix whitespace.

Modified:
    trunk/libgfortran/ChangeLog
    trunk/libgfortran/io/read.c
    trunk/libgfortran/io/transfer.c
    trunk/libgfortran/io/unit.c


-- 


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


  parent reply	other threads:[~2008-11-16 16:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 22:45 [Bug libfortran/38097] New: gfortran does not allow blanks in exponent in float (even with BN) jjcogliati-r1 at yahoo dot com
2008-11-13 15:50 ` [Bug libfortran/38097] I/O with blanks in exponent fails; blank="NULL", BN edit descriptor burnus at gcc dot gnu dot org
2008-11-14  4:34 ` jvdelisle at gcc dot gnu dot org
2008-11-16 16:15 ` jvdelisle at gcc dot gnu dot org [this message]
2008-11-16 16:21 ` jvdelisle at gcc dot gnu dot org
2008-11-16 16:24 ` jvdelisle at gcc dot gnu dot 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=20081116161343.29976.qmail@sourceware.org \
    --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).