Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!shelby!bcm!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!unmvax!ariel.unm.edu!ghostwheel.unm.edu!john
From: john@ghostwheel.unm.edu (John Prentice)
Newsgroups: alt.sys.sun
Subject: Re: How Broken is Sun Fortran (Summary)
Message-ID: <1991Feb07.230053.25074@ariel.unm.edu>
Date: 7 Feb 91 23:00:53 GMT
References: <3140@casbah.acns.nwu.edu> <1991Feb04.013025.8087@ariel.unm.edu> <1991Feb4.194628.12615@tukki.jyu.fi> <49413@seismo.CSS.GOV>
Organization: University of New Mexico, Albuquerque, NM
Lines: 23

In article <49413@seismo.CSS.GOV> stead@beno.CSS.GOV (Richard Stead) writes:
>
>> 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.
>

Unfortunately, not all of 1.3.1's problems are so simple.  Trust me, you
have something to worry about.  I hope Sun does a better job of testing 1.4
before they release it than they did 1.3.1.  The number of and nature of the
bugs in 1.3.1 are unpardonable for a Fortran compiler from  a company as
well established as Sun.  

John
--
John K. Prentice    john@unmfys.unm.edu (Internet)
Dept. of Physics and Astronomy, University of New Mexico, Albuquerque, NM, USA
Computational Physics Group, Amparo Corporation, Albuquerque, NM, USA