public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Tim Prince" <tprince@computer.org>
To: <dietrich@nmia.com>, <gcc@gcc.gnu.org>
Cc: "David E. Dietrich" <dietrich@plato.nmia.com>
Subject: Re: fortran binary reads
Date: Mon, 01 Oct 2001 07:30:00 -0000	[thread overview]
Message-ID: <00b901c14a85$9c499ba0$be65323f@amr.corp.intel.com> (raw)
In-Reply-To: <m15o146-0011gLC@plato.nmia.com>

----- Original Message -----
From: "David E. Dietrich" <dietrich@plato.nmia.com>; "David E.
Dietrich" <dietrich@nmia.com>
To: <gcc@gcc.gnu.org>
Cc: "David E. Dietrich" <dietrich@plato.nmia.com>
Sent: Monday, October 01, 2001 4:16 AM
Subject: fortran binary reads


> Dear GNU Support:
> I have a Fortran applications problem that may have an easy
solution.
> The fortran compiler that came with my Suse Linux applications
software
>
> GNU Fortran 0.5.25 20010315 (release)
>
> has problems reading standard binary data files.  These files
are the
> standard single precision --- 8 byte word length ---
climatological
> data sets used by atmospheric and ocean scientists.
>
> I think the problem may be related to the fortran compiler
assuming they
> are "c" language binary files, which I am told are different
from their
> fortran counterparts.
>
> Please advise if you know of a solution.  Thank you very much
for your
> kind consideration,
>
> Sincerely, David E. Dietrich
> dietrich@nmia.com
If you are using sequential binary files (Fortran unformatted),
your difficulty is likely to be with byte order.  AFAIK, linux
tradition avoids attempts to solve this portability problem in
the language run-time libraries, as is done in several Unix
implementations.  Please read the information on this subject
under 'info g77'.  While it would appear desirable for Fortran
compilers to support opening files with big-endian byte order, to
implement such an extension is not trivial; thus the availability
of open source packages to deal with this problem.

 gcc avoids as much as possible dealing with run-time support
libraries; if you prefer to use a linux-vendor-specific version
of gcc/g77, you might ask your vendor whether they have an
interest in dealing with the problem.

This mail-list may not be as effective a forum for your question
as one of the general Fortran-oriented lists.

      reply	other threads:[~2001-10-01  7:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-01  4:17 David E. Dietrich
2001-10-01  7:30 ` Tim Prince [this message]

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='00b901c14a85$9c499ba0$be65323f@amr.corp.intel.com' \
    --to=tprince@computer.org \
    --cc=dietrich@nmia.com \
    --cc=dietrich@plato.nmia.com \
    --cc=gcc@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).