Xref: utzoo comp.arch:6951 alt.next:259
Path: utzoo!mnetor!cxsea!ssc-vax!uw-beaver!cornell!batcomputer!itsgw!imagine!rpics!kyriazis
From: kyriazis@rpics (George Kyriazis)
Newsgroups: comp.arch,alt.next
Subject: Re: RISC v. CISC --more misconceptions
Message-ID: <1613@imagine.PAWL.RPI.EDU>
Date: 1 Nov 88 04:53:21 GMT
References: <156@gloom.UUCP> <18931@apple.Apple.COM> <40@sopwith.UUCP> <10471@s.ms.uky.edu>
Sender: news@imagine.PAWL.RPI.EDU
Reply-To: kyriazis@turing.cs.rpi.edu (George Kyriazis)
Organization: RPI CS Dept.
Lines: 28


In article <10471@s.ms.uky.edu> you write:
>Yea really ... and compilers use integer multiplies all the
>time when referencing into arrays...
>
>I for one would like to see floating point tossed out, since I
>never use it (and I happen to dislike my numerical analysis class :-)
>-- 

Floating point is getting faster and faster every day.  One example that
I know of is the AT&T DSP32 Digital Signal Processor.  It needs 1 CPU
cycle to do a floating point multiplication and accumulation.  An
interesting side-effect is in the calculation of array referencing.
It expands the array index to FP, does the array indexing, and then
truncates the resulting address to an integer.  (The compiler I am
talking about is the one that is the one that AT&T gives for their
Pixel Machine).


-- 

  George Kyriazis
  kyriazis@turing.cs.rpi.edu
------------------------------

  George Kyriazis
  kyriazis@turing.cs.rpi.edu
------------------------------