Xref: utzoo comp.sys.att:4150 comp.unix.microport:1456 comp.sys.ibm.pc:18611
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!nrl-cmf!cmcl2!phri!marob!djs!samperi
From: samperi@djs.UUCP (Dominick Samperi)
Newsgroups: comp.sys.att,comp.unix.microport,comp.sys.ibm.pc
Subject: Re: AT&T 386 UNIX Vr3.1
Message-ID: <178@djs.UUCP>
Date: 1 Sep 88 18:47:11 GMT
References: <145@carpet.WLK.COM> <441@uport.UUCP> <176@djs.UUCP> <7339@bigtex.uucp>
Reply-To: samperi@djs.UUCP (Dominick Samperi)
Organization: Village Software
Lines: 19

In article <7339@bigtex.uucp> james@bigtex.UUCP (James Van Artsdalen) writes:
|In article <176@djs.UUCP>, samperi@djs.UUCP (Dominick Samperi) wrote:
|
|> I've used AT&T's C compiler under Sys V Rel. 2 on a 3B2/300 since before
|> Microport existed, and it has NEVER caused the system to panic when I run
|> trivial programs that do some floating point operations.
|
|Nor does the Microport compiler.  Microport has been guilty of quality
|control lapses in the past, but this problem is solely Intel's.  The
|latest step of the 80386 supposedly fixes this problem.

I should have made it clear that I was speaking about their 286 compiler, for
which they have admitted that it is a compiler bug, and they have given the
work-around: "buy another vendor's C compiler."
-- 
Dominick Samperi
    samperi@acf8.nyu.edu             uunet!hombre!samperi
    cmcl2!acf8!samperi               rutgers!acf8.nyu.edu!samperi
      (^ ell)