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,183ebe04e93f0506
X-Google-Attributes: gid103376,public
X-Google-Thread: 107079,183ebe04e93f0506
X-Google-Attributes: gid107079,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: fixed point vs floating point
Date: 1997/11/22
Message-ID: <dewar.880248826@merv>#1/1
X-Deja-AN: 291693091
Distribution: inet
References: <mheaney-ya023680002211970739180001@news.ni.net>
 <EK29JB.Jor.0.-s@inmet.camb.inmet.com>
X-Complaints-To: usenet@news.nyu.edu
X-Trace: news.nyu.edu 880249000 6459 (None) 128.122.140.58
Organization: New York University
Newsgroups: comp.lang.ada,sci.math.num-analysis
Date: 1997-11-22T00:00:00+00:00
List-Id: <comp.lang.ada>


Tuck said

<<I'm not sure to what Robert is referring here.  Fixed + fixed is
as efficient as the normal integer operation, as is Fixed - Fixed,
Fixed * Integer, and Fixed / Integer.  The only operations that are
potentially inefficient are Fixed * Fixed and Fixed / Fixed, neither of which
are particularly likely when the fixed-point type represents an angle ;-).

Even if you do use Fixed * Fixed or Fixed / Fixed, the inefficiency
has to do with sometimes having to shift the result or one of the
operands after/before performing the operation (presuming binary
smalls).  If the machine has efficient shifting, this is not a major
overhead.  However, it may be that on some compilers, the fixed-fixed
multiplication/division operations are handled out-of-line, and the
procedure-call overhead is the primary added expense.
>>

Surely Tuck, you know that on almost all modern machines, integer
multiplication is much slower than floating-point multiplication?

So even without the sift, you are behind.

Sure if you never do multiplications, then the penalty for fixed-point
can be close to zero (compared with flaoting-point), unless of course
you want more than 32 bits of precision and you are on a 32 bit machine,
then fixed-point gets very expensive.