public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus 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: Thu, 13 Nov 2008 15:50:00 -0000	[thread overview]
Message-ID: <20081113154924.14093.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38097-12362@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from burnus at gcc dot gnu dot org  2008-11-13 15:49 -------
Jerry, can you have a look? Using ifort it prints:  2003.000
and it seems to be valid Fortran 95/2003.

"10.7.6 BN and BZ editing"

"The BN and BZ edit descriptors temporarily change (9.4.1) the blank
interpretation mode (9.4.5.4, 9.5.1.5) for the connection. The edit descriptors
BN and BZ set the blank interpretation mode corresponding to the BLANK=
specifier values NULL and ZERO, respectively. The blank interpretation mode
controls the interpretation of nonleading blanks in numeric input fields. Such
blank characters are interpreted as zeros when the blank interpretation mode
has the value ZERO; they are ignored when the blank interpretation mode has the
value NULL. The effect of ignoring blanks is to treat the input field as if
blanks had been removed, the remaining portion of the field right justified,
and the blanks replaced as leading blanks. However, a field containing only
blanks has the value zero.

"The blank interpretation mode affects only numeric editing (10.6.1) and
generalized numeric editing (10.6.4.1) on input. It has no effect on output."

"9.4.5.4 BLANK= specifier in the OPEN statement
"The scalar-default-char-expr shall evaluate to NULL or ZERO. The BLANK=
specifier is permitted only for a connection for formatted input/output. It
specifies the current value of the blank interpretation mode (10.7.6, 9.5.1.5)
for input for this connection. This mode has no effect on output. It is a
changeable mode (9.4.1). If this specifier is omitted in an OPEN statement that
initiates a connection, the default value is NULL."


Thus it should work with default settings. Not surprisingly (as g77 works),
BZ/BN are also part of Fortran 95.


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jvdelisle at gcc dot gnu dot
                   |                            |org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
  GCC build triplet|x86_64-redhat-linux         |
   GCC host triplet|x86_64-redhat-linux         |
 GCC target triplet|x86_64-redhat-linux         |
           Keywords|                            |wrong-code
   Last reconfirmed|0000-00-00 00:00:00         |2008-11-13 15:49:23
               date|                            |
            Summary|gfortran does not allow     |I/O with blanks in exponent
                   |blanks in exponent in float |fails; blank="NULL", BN edit
                   |(even with BN)              |descriptor


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


  reply	other threads:[~2008-11-13 15:50 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 ` burnus at gcc dot gnu dot org [this message]
2008-11-14  4:34 ` [Bug libfortran/38097] I/O with blanks in exponent fails; blank="NULL", BN edit descriptor jvdelisle at gcc dot gnu dot org
2008-11-16 16:15 ` jvdelisle at gcc dot gnu dot org
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=20081113154924.14093.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).