public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "huwaldtj at saic dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37129] Problems with access='direct', recl=1 I/O
Date: Fri, 15 Aug 2008 17:00:00 -0000 [thread overview]
Message-ID: <20080815165857.27066.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37129-16600@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from huwaldtj at saic dot com 2008-08-15 16:58 -------
(In reply to comment #1)
Is there a Fortran 77 compatible work-around that will do what this program was
doing (i.e.: write out a mixed set of 4 byte integers and 8 byte floats to a
binary file with a specific format since that file will be read by another
program that we do not control)?
Joe
> (In reply to comment #0)
>
> > It appears that gfortran does not interpret recl=1 the way many historic
> > compilers, including g77, did. So, this bug report is to request that recl=1
> > be interpreted to mean that the compiler should use the I/O list to determine
> > how many items to read or write as g77 apparently did.
>
> I suspect that gfortran intreprets recl=1 in your open statement
> according to the words of the Fortran Standard. If my reading
> of 9.4.5.12 is correct (which can be incorrect), then it appears
> the code is nonconforming Fortran and it is a bug in the code
> not gfortran.
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37129
next prev parent reply other threads:[~2008-08-15 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 14:17 [Bug fortran/37129] New: " huwaldtj at saic dot com
2008-08-15 16:54 ` [Bug fortran/37129] " kargl at gcc dot gnu dot org
2008-08-15 17:00 ` huwaldtj at saic dot com [this message]
2008-08-15 19:01 ` kargl at gcc dot gnu dot org
2008-08-16 22:50 ` jvdelisle at gcc dot gnu dot org
2008-08-17 18:01 ` burnus at gcc dot gnu dot org
2008-08-17 19:55 ` kargl at gcc dot gnu dot org
2008-08-19 2:41 ` 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=20080815165857.27066.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).