This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: g77 of egcs-1.0.2/1.0.3a returns exit code 1 for argument typemismatch
- To: Mako Sasaki <sasaki at tyo dot sci dot jri dot co dot jp>
- Subject: Re: g77 of egcs-1.0.2/1.0.3a returns exit code 1 for argument typemismatch
- From: Toon Moene <toon at moene dot indiv dot nluug dot nl>
- Date: Wed, 29 Jul 98 20:00:35 +0200
- Cc: egcs-bugs at cygnus dot com
- Organization: Moene Computational Physics, Maartensdijk, The Netherlands
- References: <199807290916.SAA28381@tnlx1.sci.jri.co.jp>
> I got a non-zero exit status from g77 in egcs-1.0.2 and
> egcs-1.0.3a for a Fortran source shown below, and could
> not get any object.
> Is this a bug in g77/egcs or an expected behavior ?
subroutine AA( a,b,c,i )
...
subroutine BB( a,b,c,d )
...
call AA( a,b,c,d )
...
Yes, this is not allowed and hence g77's behaviour is expected.
However, when compiling the routines separately, this cannot be
detected - that's why you normally get away with it. You can get it
compiled using -fno-globals, but you're on your own wrt correct
execution of this code.
Note that the error message explains how you can find this (and
more) information: [info -f g77 M GLOBALS].
HTH,
Toon.