Xref: utzoo alt.sys.sun:2642 comp.lang.fortran:4688
Path: utzoo!utgpu!cs.utexas.edu!helios!bcm!dimacs.rutgers.edu!seismo!beno!stead
From: stead@beno.CSS.GOV (Richard Stead)
Newsgroups: alt.sys.sun,comp.lang.fortran
Subject: Re: How Broken is Sun Fortran (Summary)
Message-ID: <49413@seismo.CSS.GOV>
Date: 6 Feb 91 20:38:29 GMT
References: <3140@casbah.acns.nwu.edu> <1991Feb04.013025.8087@ariel.unm.edu> <1991Feb4.194628.12615@tukki.jyu.fi>
Sender: usenet@seismo.CSS.GOV
Followup-To: alt.sys.sun
Lines: 26

In article <1991Feb4.194628.12615@tukki.jyu.fi>, eloranta@tukki.jyu.fi (Jussi Eloranta) writes:
> 
> on Fortran 1.3.1 I've found the following problems:
> 
> 1) Sometimes loader complains about mysterious 'mcount' symbol...
>    I checked the program and it didn't have a symbol with that name.

[ one more specific complaint, and some vague complaints deleted ]

I don't know about your other complaints, but this one is due to compiling
some of your code for profiling, but linking it non-profiling.  The mcount
variable is used by the profiler.  Compile and link your code either with
or without profiling, but don't mix it.  This is not specific to Fortran 1.3.1.

> And all these were found during 4 days. So there is probably more to come :-(

If they are all like this first one, the rest of us have nothing to worry
about.

> And they call it fortran compiler ...?

No, the thing that uses mcount they call a profiler.

Richard Stead
Center for Seismic Studies
stead@seismo.css.gov