From: Benjamin Joseph <benjo@u.washington.edu>
To: Bud Davis <bdavis9659@comcast.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Ancient Fortran, help please
Date: Sun, 19 Dec 2004 03:48:00 -0000 [thread overview]
Message-ID: <Pine.A41.4.61b.0412181948200.91898@dante76.u.washington.edu> (raw)
In-Reply-To: <1103416536.21610.13.camel@localhost.localdomain>
That worked!
Thank you,
-Ben
On Sat, 18 Dec 2004, Bud Davis wrote:
> On Sat, 2004-12-18 at 13:22, Benjamin Joseph wrote:
>
>>
>> It looks like it's just defining a variable TYPE with a character array.
>> Anyway, as far as compilability is concerned, this works for Intel Fortran
>> Compiler 8.1.
>>
>
> TYPE is declared by default to be of type REAL*8 by the IMPLICIT REAL
> statement on line 2.
>
> the Intel compiler is quite forgiving. to work with g77 you will have to
> declare TYPE to be of an INTEGER or CHARACTER type.
>
> It should be a very surgical and safe change, as it makes no sense
> to either use or set TYPE(1) with a double precision real :)
>
> BLOCK DATA BNCSRC
> IMPLICIT REAL*8 (A-H,O-Z)
> INTEGER*8 TYPE
>
>
> there is good information in the g77 info page concerning
> running code from other fortran compilers. -finit-local-zero
> and -fno-automatic are two options that are defaults for other
> compilers. you might want to think about these a bit before
> digging deep into the code if the runtime results are not as
> expected. nothing to do with the current issue, just something to keep
> in mind.
>
> don't let this little incompatibility dissuade you from using
> g77. IMHO g77 is the most robust and flexible F77 compiler
> available.
>
>
> HTH,
> bud davis
>
>
>
>
>
>
>
next prev parent reply other threads:[~2004-12-19 3:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-18 9:54 Bud Davis
2004-12-18 19:22 ` Benjamin Joseph
2004-12-19 0:35 ` Bud Davis
2004-12-19 3:48 ` Benjamin Joseph [this message]
2004-12-19 9:57 ` custom CPU porting : guidance please sashti srinivasan
2004-12-20 6:17 ` Sriharsha
2004-12-23 18:25 ` sashti srinivasan
2004-12-23 18:33 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
2004-12-18 4:51 Ancient Fortran, help please Benjamin Joseph
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=Pine.A41.4.61b.0412181948200.91898@dante76.u.washington.edu \
--to=benjo@u.washington.edu \
--cc=bdavis9659@comcast.net \
--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).