Path: utzoo!utgpu!cunews!bnrgate!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: reg@afwl.af.mil (Reg Clemens)
Newsgroups: comp.sys.sun
Subject: SunFortran v1.4 BUGS.
Keywords: No Digest Subjects in Unmoderated Mode
Message-ID: <3389@brchh104.bnr.ca>
Date: 4 Jun 91 18:40:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sunspots, Psuedo-Unmoderated
Lines: 40
Approved: sun-spots@rice.edu
X-Original-Date:    Sun, 19 May 91 20:40:54 MDT

OK folks, guess its time to start enumerating the bugs in the new
release of SunFortran [ SunFortran v1.4 ].

From what I've seen so far the compiler is much better than 1.3.1 and
1.4beta.

That said, my first test was to compile the SLATEC Math library, and
there were several failures.  [ for those of you not familiar with
SLATEC, it currently stands at about 270000 lines of Fortran, and contains
a set of Quick Checks that amount to another 44000 lines of code.
It is used on everything from PCs to CRAYs ]

From what I've seen so far, there still seem to be optimizer problems,
so if you want the right answer (as opposed to the wrong answer
but much faster) you should NOT turn on the optimizer.
Pity, since some of the QC were speeded up anywhere from 2x to 5x by
saying -O or -fast.

So, to date I have seen THREE failures.  Two are related to COMPLEX ARITHMETIC,
and the third is not.  The two bugs involving COMPLEX cause the codes
to blow off the machine [ at least you know you have a problem ], the
other one only occurs with -fast and just gives the wrong answer...
I have not investigated it in detail yet, but it could be just due to the
(documented) fact that -fast handles underflow differently.

Examples of the two COMPLEX ARITHMETIC bugs follow.  The first will occur
when the code is compiled with either -O or -fast.  The other one only
with -fast.

*** BUG 1 ***

The following piece of code demos a problem with AIMAG.  In the  actual
code AIMAG was not on a WRITE statement, but putting it theres makes things
easier to demo.  Note that the code `does the right thing' for -g and
[no optimization] but dies for -O or -fast.  The problem seems related to
the fact that `C' is dimensioned, since if you un-dimension C (four places)
this test will run correctly for all optimization levels.

Environment: SS2, SUNOS4.1.1, SunFortran v1.4