From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-346745-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 13481 invoked by alias); 9 Feb 2011 17:12:00 -0000
Received: (qmail 13471 invoked by uid 22791); 9 Feb 2011 17:11:58 -0000
X-SWARE-Spam-Status: No, hits=-2.7 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Received: from localhost (HELO gcc.gnu.org) (127.0.0.1)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 09 Feb 2011 17:11:54 +0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47667] New: I/O for reals: READ waits for input after "i" and "n"
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-47667-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Date: Wed, 09 Feb 2011 17:20:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2011-02/txt/msg01211.txt.bz2

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

           Summary: I/O for reals: READ waits for input after "i" and "n"
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: burnus@gcc.gnu.org
                CC: jvdelisle@gcc.gnu.org


Based on
https://www.jiscmail.ac.uk/cgi-bin/webadmin?A1=ind1102&L=COMP-FORTRAN-90#2

If one uses:
  READ (*,*) real_variable
and enters "i"<enter> or "n"<enter>, gfortran does not immediately return with
an error but waits for further input. As it does not accept "N"<enter>"aN" but
only "NaN" and "Inf"/"Infinity" as input, this behaviour does not not make
sense.

For other characters, e.g. "e" or "d" it immediately returns with an error.

Expected: As NAG, ifort, pathf95 do (for the linked test case):

  -9.9900000E+02
 Input new value:
i
  ioerr =  140         a =   -9.9900000E+02


Result with gfortran (note extra input line):

  -999.00000
 Input new value:
i

  ioerr =         5010         a =   -999.00000
 Input new value:
i
nf
  ioerr =         5010         a =   -999.00000