From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f8362,c7637cfdf68e766 X-Google-Attributes: gidf8362,public X-Google-Thread: 103376,c7637cfdf68e766 X-Google-Attributes: gid103376,public X-Google-Thread: 109d8a,c7637cfdf68e766 X-Google-Attributes: gid109d8a,public X-Google-Thread: 107079,c7637cfdf68e766 X-Google-Attributes: gid107079,public X-Google-Thread: f43e6,c7637cfdf68e766 X-Google-Attributes: gidf43e6,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: floating point comparison Date: 1997/08/18 Message-ID: #1/1 X-Deja-AN: 265064996 Distribution: inet References: <33E61497.33E2@pseserv3.fw.hac.com> <5sar4r$t7m$1@cnn.nas.nasa.gov> <5sbb90$qsc@redtail.cruzio.com> <33ECA115.13DE@math.okstate.edu> <5t5976$rle$1@ccioffe.ioffe.rssi.ru> Organization: New York University Newsgroups: comp.lang.ada,sci.math.num-analysis,comp.software-eng,comp.theory,sci.math Date: 1997-08-18T00:00:00+00:00 List-Id: Andrew says << Strongly disagree. There ARE roundoff errors even in the IEEE 754 arithemtic model. Moreover, the standard clearly specifies rounding models.>> You completely miss the point I am making. There are no *errors*, the discrepancies between IEEE arithmetic and real arithmetic are not errors, they are simply differences that come from two different arithmetic models. When we have integer arithmetic and we divide 10 by 3 to get 3, we do not say this is an error. The result is different from the mathematical value of 10.0/3.0, but there is no error here, just a different arithmetic model. I know perfectly well that the phrase "rounding error" is well established, but my point is that calling it an error leads people into the niave trap of thinking of floating-point arithmetic as being real arithmetic. In fact I received quite a few email messages, from some quite interesting people :-) saying that they agreed that it was a pity that the term rounding error had ever got into the literature, but of course it is much too entrnched to get rid of. But your repsonse tends to make me think that you are indeed fallling into the trap of thinking of these xdiscepancies as errors. It's a mistake! As for your comment about different register lengths etc. This is a matter of binding of the language you are using to IEEE. The set of IEEE operatoins contains no such uncertainty, and a decent binding of a high level language to IEEE (e.g. SANE from Apple) must avoid such uncertainties.