public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/31099]  New: Runtime error on legal code using RECL
Date: Fri, 09 Mar 2007 10:05:00 -0000	[thread overview]
Message-ID: <bug-31099-10259@http.gcc.gnu.org/bugzilla/> (raw)

$ cat a.f90 
 PROGRAM TEST
   INTEGER :: A
   OPEN(10, FORM="UNFORMATTED", RECL=1024)
   A = -1
   WRITE(10) A
 END PROGRAM TEST

$ gfortran a.f90 && ./a.out            
At line 5 of file a.f90
Fortran runtime error: I/O past end of record on unformatted file
$ pgf90 a.f90 && ./a.out && xxd fort.10  
0000000: 0400 0000 ffff ffff 0400 0000            ............
$ sunf90 a.f90 && ./a.out && xxd fort.10
0000000: 0400 0000 ffff ffff 0400 0000            ............
$ ifort a.f90 && ./a.out && xxd fort.10 
0000000: 0400 0000 ffff ffff 0400 0000            ............


-- 
           Summary: Runtime error on legal code using RECL
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: normal
          Priority: P3
         Component: libfortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: fxcoudert at gcc dot gnu dot org


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


             reply	other threads:[~2007-03-09 10:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-09 10:05 fxcoudert at gcc dot gnu dot org [this message]
2007-03-09 10:06 ` [Bug libfortran/31099] [4.3/4.2 regression] " fxcoudert at gcc dot gnu dot org
2007-03-09 12:29 ` burnus at gcc dot gnu dot org
2007-03-09 12:56 ` burnus at gcc dot gnu dot org
2007-03-09 18:02 ` jvdelisle at gcc dot gnu dot org
2007-03-09 20:13 ` Thomas dot Koenig at online dot de
2007-03-09 21:30 ` patchapp at dberlin dot org
2007-03-09 21:51 ` jvdelisle at gcc dot gnu dot org
2007-03-09 23:55 ` jvdelisle at gcc dot gnu dot org
2007-03-10  0:01 ` jvdelisle at gcc dot gnu dot org
2007-03-10  0:03 ` jvdelisle at gcc dot gnu dot org
2007-03-10  0:05 ` jvdelisle at gcc dot gnu dot org
2007-03-14  9:05 ` jellby at yahoo dot com
2007-03-16  0:04 ` jvdelisle at gcc dot gnu dot org
2007-03-16  0:41 ` jvdelisle at gcc dot gnu dot org
2007-03-16  1:11 ` jvdelisle at gcc dot gnu dot org
2007-03-16  1:54 ` jvdelisle at gcc dot gnu dot org
2007-03-16  1:57 ` jvdelisle at gcc dot gnu dot org
2007-04-02 21:49 ` burnus at gcc dot gnu dot org
2007-04-03  0:04 ` jvdelisle at gcc dot gnu dot org
2007-04-25 21:39 ` tkoenig 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=bug-31099-10259@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).