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: 103376,c7637cfdf68e766 X-Google-Attributes: gid103376,public X-Google-Thread: f8362,c7637cfdf68e766 X-Google-Attributes: gidf8362,public X-Google-Thread: f43e6,c7637cfdf68e766 X-Google-Attributes: gidf43e6,public X-Google-Thread: 109d8a,c7637cfdf68e766 X-Google-Attributes: gid109d8a,public X-Google-Thread: 107079,c7637cfdf68e766 X-Google-Attributes: gid107079,public From: nesterov@holo.ioffe.rssi.ru (Andrew V. Nesterov) Subject: Re: floating point comparison Date: 1997/08/16 Message-ID: <5t5976$rle$1@ccioffe.ioffe.rssi.ru>#1/1 X-Deja-AN: 265013225 References: <33E61497.33E2@pseserv3.fw.hac.com> <5sar4r$t7m$1@cnn.nas.nasa.gov> <5sbb90$qsc@redtail.cruzio.com> <33ECA115.13DE@math.okstate.edu> Distribution: inet Organization: Ioffe Phys-Tech Institute Newsgroups: comp.lang.ada,sci.math.num-analysis,comp.software-eng,comp.theory,sci.math Date: 1997-08-16T00:00:00+00:00 List-Id: In article , dewar@merv.cs.nyu.edu (Robert Dewar) wrote: [snip] >If we are talking about IEEE floating-point, the operations have no errors >at all. There are no rounding errors or anything else in the arithemtic >model defined in this standard. Strongly disagree. There ARE roundoff errors even in the IEEE 754 arithemtic model. Moreover, the standard clearly specifies rounding models. > >The results of the operations are exactly well defined to the last bit (*) >and must be the same on all machines. > Could be different due to unspecified length of the register or extended precision numbers or rounding model chosen. > [snip] > >I really dislike the term "rounding error". Error is a loaded term which >somehow indicates that something is wrong. When you take two IEEE numbers >and do an addition, you get a precise answer, with no error. Perhaps a >term like "real discrepancy" would be better, and would help avoid >propagating the dangerous impression that floating-point arithmetic *is* >real arithmetic that does not work right. When two representable (i.e. having no roundoff error) IEEE numbers are added the result could be rounded, that is true result cannot be stored as exact IEEE number. Similarly, results of other operations (multiplications, square roots, etc) could be rounded. Concidering the term itself, it sounds to me reasonably adequate. As far as I could see, and since I am not native english I could be wrong, the term means "an error result from a roundoff", i.e. a floating point number is approximate estimate to a precise number. Well, I better refer to J.Wilkinson books, he used the term many times and thought nothing is wrong with it. [snip] -- Andrew.