Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83 based; site hou2b.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxj!mhuxt!houxm!hou2b!dwc
From: dwc@hou2b.UUCP (D.CHEN)
Newsgroups: net.arch
Subject: risc, cisc, and microprogramming
Message-ID: <557@hou2b.UUCP>
Date: Sun, 16-Jun-85 00:22:41 EDT
Article-I.D.: hou2b.557
Posted: Sun Jun 16 00:22:41 1985
Date-Received: Mon, 17-Jun-85 04:05:25 EDT
Organization: AT&T Bell Labs, Holmdel NJ
Lines: 9

> A reasonable approach to producing CISC machines, then, would be to have the
> compiler writers design the instruction set; and to have the instruction set
> be changeable for different languages.

funny how things come full circle.  one way to implement the above is to
have dynamically loaded microprogrammed instruction sets.  but as dave
paterson mentions in his paper (i think), the difficulty of writing
and supporting microprograms along with the time penalty in using
microprogrammed logic (versus hardwired logic) led to the RISC idea.