Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!nsc!voder!apple!baum
From: baum@apple.UUCP (Allen J. Baum)
Newsgroups: comp.arch
Subject: Re: RISC  a short answer??
Message-ID: <7553@apple.UUCP>
Date: 6 May 88 18:45:18 GMT
References: <1036@nusdhub.UUCP> <1988May3.224604.2252@utzoo.uucp> <383@m3.mfci.UUCP> <1988May5.171444.849@utzoo.uucp> <9341@apple.Apple.Com>
Reply-To: baum@apple.UUCP (Allen Baum)
Organization: Apple Computer, Inc.
Lines: 20

--------
[]
>In article <9341@apple.Apple.Com> bcase@apple.UUCP (Brian Case) writes:
>
>I disagree completely.  I think the whole point of RISC is to properly
>match hardware with the capabilities of software .....
>I plan on posting a summary of RISC-related literature , but let me now
>give my personal, back-of- the-business-card summary of RISC:
>.....
>2)  Good match to optimizing compiler technology (the architecture makes it
>easy for the compiler in several ways:  code generation, code motion,
>register allocation, etc., and *calculating the cost of code sequences* in
>both time and space)

Note that 20 years ago, compiler technology was not at the state that current
RISC technology could be used. Five years ago, it wasn't at the state that
VLIW hardware could be used. Hmm, can you determine a historical trend from
these facts?

--
{decwrl,hplabs,ihnp4}!nsc!apple!baum		(408)973-3385