public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jblomqvi at cc dot hut dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/21621] Inconsistency with binary sequential output
Date: Tue, 24 May 2005 20:33:00 -0000	[thread overview]
Message-ID: <20050524200233.22594.qmail@sourceware.org> (raw)
In-Reply-To: <20050517134432.21621.P.Schaffnit@access.rwth-aachen.de>


------- Additional Comments From jblomqvi at cc dot hut dot fi  2005-05-24 20:02 -------
Well no, the standard does not specify how unformatted sequential record markers
are implemented. In short, gfortran uses markers of type off_t, which is 64 bits
on operating systems with large file (LFS) support. Today, that is most OS:es in
common use. g77 AFAIK uses markers of type long, that is 32-bits on most 32-bit
platforms and 64 bits on 64-bit platforms. See also PR 19303. Also note that Bud
Davis is apparently currently working on pluggable record markers, which should
allow gfortran to add some kind of g77 compatibility flag.

-- 


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


  parent reply	other threads:[~2005-05-24 20:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17 13:49 [Bug libfortran/21621] New: " P dot Schaffnit at access dot rwth-aachen dot de
2005-05-17 17:31 ` [Bug libfortran/21621] " pinskia at gcc dot gnu dot org
2005-05-19 16:44 ` tobi at gcc dot gnu dot org
2005-05-19 16:45 ` tobi at gcc dot gnu dot org
2005-05-23  9:06 ` P dot Schaffnit at access dot rwth-aachen dot de
2005-05-24 20:33 ` jblomqvi at cc dot hut dot fi [this message]
2005-05-31  2:37 ` bdavis9659 at comcast dot net
2005-05-31  2:45 ` pinskia 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=20050524200233.22594.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).