From: hjstein@bfr.co.il (Harvey J. Stein)
To: egcs@egcs.cygnus.com
Cc: hjstein@bfr.co.il
Subject: g77 plans - support for automatic, .eq. for logicals, etc?
Date: Thu, 11 Mar 1999 02:26:00 -0000 [thread overview]
Message-ID: <m21ziwgw5u.fsf@blinky.bfr.co.il> (raw)
In-Reply-To: abel@bfr.co.il's message of "11 Mar 1999 12:18:47 +0200"
We're still using f2c because it's more friendly for our code.
Specifically:
1. The AUTOMATIC keyword for forcing allocation of specified variables
on the stack instead of statically is not supported by g77.
2. G77 requires .EQV. & .NEQV. to be used for comparing logicals,
whereas most other Fortran compilers accept the use of .EQ. and
.NE. without comment.
3. G77 chokes on certain implicit do loops in DATA statements that
other Fortran compilers accept without comment.
4. f2c + my f2c-stabs package works better under gdb (inside of emacs)
for viewing variables than g77 with gdb.
I'm not sure if this is a complete list, but it's most of the reason
why we're unable to switch to g77 from f2c.
Are there any plans for addressing these points, or are we forced to
either keep using f2c? BTW, because of compilation standards on other
platforms (not to mention the size of the changes required), we can't
solve 1 by compiling with the flag to make all variables automatic
except for those mentioned in a STATIC line.
--
Harvey J. Stein
BFM Financial Research
hjstein@bfr.co.il
WARNING: multiple messages have this Message-ID
From: hjstein@bfr.co.il (Harvey J. Stein)
To: egcs@egcs.cygnus.com
Cc: hjstein@bfr.co.il
Subject: g77 plans - support for automatic, .eq. for logicals, etc?
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <m21ziwgw5u.fsf@blinky.bfr.co.il> (raw)
Message-ID: <19990331234600.PFx_SzOVADkijeZCEJS0Xer3B4Mv-r_0LST_wiIaf_s@z> (raw)
We're still using f2c because it's more friendly for our code.
Specifically:
1. The AUTOMATIC keyword for forcing allocation of specified variables
on the stack instead of statically is not supported by g77.
2. G77 requires .EQV. & .NEQV. to be used for comparing logicals,
whereas most other Fortran compilers accept the use of .EQ. and
.NE. without comment.
3. G77 chokes on certain implicit do loops in DATA statements that
other Fortran compilers accept without comment.
4. f2c + my f2c-stabs package works better under gdb (inside of emacs)
for viewing variables than g77 with gdb.
I'm not sure if this is a complete list, but it's most of the reason
why we're unable to switch to g77 from f2c.
Are there any plans for addressing these points, or are we forced to
either keep using f2c? BTW, because of compilation standards on other
platforms (not to mention the size of the changes required), we can't
solve 1 by compiling with the flag to make all variables automatic
except for those mentioned in a STATIC line.
--
Harvey J. Stein
BFM Financial Research
hjstein@bfr.co.il
next reply other threads:[~1999-03-11 2:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-11 2:26 Harvey J. Stein [this message]
[not found] ` < m21ziwgw5u.fsf@blinky.bfr.co.il >
1999-03-11 8:02 ` craig
1999-03-31 23:46 ` craig
1999-03-31 23:46 ` Harvey J. Stein
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=m21ziwgw5u.fsf@blinky.bfr.co.il \
--to=hjstein@bfr.co.il \
--cc=egcs@egcs.cygnus.com \
/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).