Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool2.mu.edu!sol.ctr.columbia.edu!cunixf.cc.columbia.edu!cunixd.cc.columbia.edu!mjf
From: mjf@cunixd.cc.columbia.edu (Michael J Flory)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: v09i191: popadbug, test for 386 CPU bug
Summary: Anyone's machine *not* fail?
Message-ID: <1991Jan5.000042.19703@cunixf.cc.columbia.edu>
Date: 5 Jan 91 00:00:42 GMT
References: <336@aplcomm.JHUAPL.EDU>
Sender: news@cunixf.cc.columbia.edu (The Daily News)
Organization: Columbia University
Lines: 11


Tried the POPADBUG test on two clones -- my 20MHZ Tangent with 387 (about
six months old) and a colleague's year-old Northgate (20MHz? with 387) -- 
both failed.  Didn't get time to try it on a new '486...  Anyone with a
386 that passed?  I've run a suite of stat tests on my machine and the
output is perfect, and I've never had mysterious crashes.  Perhaps the 
compilers in use never load the stack in the manner tested by POPADBUG?
(If that doesn't make sense it's because I'm well out of my depth...) BTW,
both machines behaved fine after running the test.

-- Michael Flory (mjf@cunixd.cc.columbia.edu)