Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!munnari.oz.au!goanna!ok
From: ok@goanna.cs.rmit.oz.au (Richard A. O'Keefe)
Newsgroups: comp.arch
Subject: Re: IEEE floating point
Keywords: Various contributors have discussed the pros and cons of IEEE FP
Message-ID: <6024@goanna.cs.rmit.oz.au>
Date: 29 May 91 07:13:38 GMT
Article-I.D.: goanna.6024
References: <9105250030.AA08036@ucbvax.Berkeley.EDU> <5397@network.ucsd.edu> <4451@inews.intel.com>
Organization: Comp Sci, RMIT, Melbourne, Australia
Lines: 12

In article <4451@inews.intel.com>, news@inews.intel.com (news accounting id) writes:
>  What you should do is use interval arithmetic.  It uses twice the
>  memory and less than 3 times the time*gates.   By using interval
>  arithmetic you at least know when something is messed up.  In fact,
>  used typed data and you'll know if your algorithms make sense.

Support for Interval arithmetic is precisely why IEEE arithmetic includes
all those rounding modes.
-- 
Should you ever intend to dull the wits of a young man and to
incapacitate his brains for any kind of thought whatever, then
you cannot do better than give him Hegel to read.  -- Schopenhauer.