Xref: utzoo comp.unix.ultrix:5144 comp.sys.sgi:6577 comp.sys.mips:1138
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!umich!dgsi!brian
From: brian@cimage.com (Brian Kelley)
Newsgroups: comp.unix.ultrix,comp.sys.sgi,comp.sys.mips
Subject: Re: Another C compiler bug
Message-ID: <1990Nov1.153433.4006@cimage.com>
Date: 1 Nov 90 15:34:33 GMT
References: <11565@sybase.sybase.com>
Reply-To: brian@dgsi.UUCP (Brian Kelley)
Organization: Cimage Corp, Ann Arbor, MI
Lines: 26

In article <11565@sybase.sybase.com> mcfong@mercury.sybase.com () writes:
>I get the following results on the following MIPS-based systems:
>
>	RISC ULTRIX 3.0			7e-7 = 0.000000
>	SGI IRIX 3.2			7e-7 = 0.000000
>	MIPS OS 1.0			7e-7 = 0.000001
>
>Looks like yet another compiler bug which MIPS has fixed but DEC and
>SGI have not yet picked up.
>
>Would someone please run the same program on the latest version of RISC
>ULTRIX (4.0) and SGI IRIX (3.3) and see if DEC or SGI have fixed the
>problem in their later releases?

I just ran it under 4.0, and sure enough:

	RISC ULTRIX 4.0			7e-7 = 0.000000

I think the main problem is ULTRIX 4.0 is using version 2.00 of the MIPS
C compiler.  Version 2.10 probably fixes this bug (I know it fixes several
others).  We are in the process of trying to get 2.10 from DEC.  It isn't
clear which version 4.1 will ship with.


---
brian@cimage.com