From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.5-pre1 Date: 22 Sep 93 17:54:38 GMT From: cis.ohio-state.edu!math.ohio-state.edu!sdd.hp.com!col.hp.com!csn!news.sin et.slb.com!news.london.sinet.slb.com!news@ucbvax.Berkeley.EDU (Mathew Lodge) Subject: Re: Problems with Alsys 386 V5.1.1 Compiler Message-ID: <27q3gu$rbg@snlsu1.london.sinet.slb.com> List-Id: In article 51b@issi-gw.issi.com, houston@issi.com (Sam Houston) writes: > In article AA25446@cs.utexas.edu, CZinsmeyer%TSS%SwRI05@D26VS046A.CCF.SwRI.ED U () writes: > >I'm developing an application for the U.S. Air Force > > After some period of time, usually twenty minutes or > >so, the system begins to slow down. The longer the system runs the slower > >things get. > > I remember hearing of a similar problem in the development of the > Patriot Missle system. It had something to do with floating point > precision and the clock. I don't remeber the details, but you > might want to see if you can find the information. I thought that the Patriot Missile system got *less accurate* as time went by, since in some calculation they were dividing through by the elapsed time using fixed point arithmetic. As time went by, the elapsed time counter got larger, a nd so more and more precision was lost on the divide. That's the version I heard... anyone really know? I really don't think it is in any way related to the Alsys bug. > Sam Houston Mat --- | Mathew Lodge | "There's nothing intellectual about wandering | | lodge@ferndown.ate.slb.com | around Italy in a big shirt trying to get | | Schlumberger Technologies, | laid" -- Blackadder on the romantic poets | | ATE division, Ferndown, UK | I speak for me, not Schlumberger Technologies |