From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Hassan Aurag <aurag@cae.com>
Cc: GCC Help Mailing List <gcc-help@gcc.gnu.org>
Subject: Re: Endianess and Fortran
Date: Tue, 06 Nov 2001 15:09:00 -0000 [thread overview]
Message-ID: <3BF574AA.DCE48080@moene.indiv.nluug.nl> (raw)
In-Reply-To: <1005925116.21445.6.camel@l0553lnx>
Hassan Aurag wrote:
> This is new to me. What are the things to watch when dealing with
> porting Fortran programs from old big-endian machines to Linux on Intel?
>
> I heard EQUIVALENCE statements are a problem. What are the other things
> to watch for?
>
> Any help or pointer to Fortran related issues is welcome.
Well, it's hard to enumerate all the possible problems with switching to
a system with a different endianness than your original one.
There's one problem we *always* hear about: It is not possible to read
unformatted files produced on your old system on your new system.
So transfer any needed data by writing it out as formatted data.
Hope this helps,
--
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)
prev parent reply other threads:[~2001-11-16 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-06 8:03 Hassan Aurag
2001-11-06 15:09 ` Toon Moene [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=3BF574AA.DCE48080@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=aurag@cae.com \
--cc=gcc-help@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).