Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 alpha 4/15/85; site ucbvax.ARPA Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!ucbvax!mwm From: mwm@ucbvax.ARPA (Mike (I'll be mellow when I'm dead) Meyer) Newsgroups: net.arch Subject: Re: RISC/CISC - IBM mainframes Message-ID: <8213@ucbvax.ARPA> Date: Sat, 15-Jun-85 21:00:24 EDT Article-I.D.: ucbvax.8213 Posted: Sat Jun 15 21:00:24 1985 Date-Received: Sun, 16-Jun-85 03:21:45 EDT References: <1452@ecsvax.UUCP> <1062@peora.UUCP> Reply-To: mwm@ucbvax.UUCP (Mike (I'll be mellow when I'm dead) Meyer) Organization: Missionaria Phonibalonica Lines: 19 In article <1062@peora.UUCP> jer@peora.UUCP (J. Eric Roskos) writes: >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. Burroughs will be glad to sell you a machine that implements that idea. Just goes to show (once again) that quality and market share are unrelated. >This could be extended by having the >instruction set be further changeable by the individual user, or automatically >by a program that analyzes instruction usage and moves frequently-used >instructions into microcode (vertical migration). Like the BBN C/70 box? Once again, ...