Path: utzoo!attcan!uunet!samsung!usc!ucsd!helios.ee.lbl.gov!nosc!marlin!aburto
From: aburto@marlin.NOSC.MIL (Alfred A. Aburto)
Newsgroups: comp.sys.amiga.tech
Subject: Re: MC68881/2 Support (hello, Dave Haynie)
Message-ID: <1430@marlin.NOSC.MIL>
Date: 4 Jun 90 19:37:20 GMT
References: <1181@metaphor.Metaphor.COM> <11996@cbmvax.commodore.com> <1183@metaphor.Metaphor.COM> <10341@batcomputer.tn.cornell.edu>
Reply-To: aburto@marlin.nosc.mil.UUCP (Alfred A. Aburto)
Distribution: comp.sys.amiga.tech
Organization: Naval Ocean Systems Center, San Diego
Lines: 22
X-Local-Date: 4 Jun 90 12:37:20 PDT

In article <10341@batcomputer.tn.cornell.edu> riley@tcgould.tn.cornell.edu (Daniel S. Riley) writes:

>In article <1183@metaphor.Metaphor.COM> djh@dragon.metaphor.com (Dallas J. Hodgson) writes:
>>As long as developers keep on using Motorola FFP as their standard,
>>(and they will unless precision requirements demand otherwise) we're gonna
>reason?
>
>-Dan Riley (riley@tcgould.tn.cornell.edu, cornell!batcomputer!riley)
>-Wilson Lab, Cornell University

Yes, the IEEESP (single precision) software floating-point libraries
(so I've been told) are being designed with the goal to be as quick
or quicker than the MathFFP but yet have an accuracy equivalent to that
of the 68881/68882 (Single Precision).  Once this goal is achieved (and I
think C-A is getting close) then I think the MathFFP will be, and should be,
weaned out of the system.  That number of math libraries is reduced
by two and we wind up with IEEESP libraries quicker and more accurate than
the MathFFP.


Al Aburto
aburto@marlin.nosc.mil