Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!seismo!ut-sally!utah-cs!utah-gr!uplherc!esunix!bpendlet
From: bpendlet@esunix.UUCP
Newsgroups: comp.arch
Subject: Re: vliw comuputers
Message-ID: <363@esunix.UUCP>
Date: Thu, 18-Jun-87 10:17:50 EDT
Article-I.D.: esunix.363
Posted: Thu Jun 18 10:17:50 1987
Date-Received: Sat, 20-Jun-87 10:07:48 EDT
References: <7082@mimsy.UUCP>
Organization: Evans & Sutherland, Salt Lake City, Utah
Lines: 34

in article <7082@mimsy.UUCP>, rab@mimsy.UUCP (Bob Bruce) says:
> 
> 
> I recently read a paper on a `very_long_instruction_word'
> (VLIW) computer, specifically the Multiflow TRACE computer.

Read "BullDog: A Compiler for VLIW Architectures" by John R. Ellis,
The MIT Press.

This was the 1985 ACM Doctoral Dissertation for 1985.

Or read the proceedings of the SIGMICRO annual workshop on microprogramming
for the last 19 years.
> 
> As memory prices continue to decline, this kind of  computer may

If you look inside of most CISC computers you will find a custom designed
LIW or VLIW computer. As far as I can tell VLIW is another way of saying
horizontal microcode. But everyone "knows" that no compiler can generate
horizontal microcode! So maybe thats why they decided to call it VLIW.

Of course most microcoded machines are optimized to emulate a specific
instruction set rather than executing application programs.

> 
> rab@mimsy.umd.edu
> seismo!mimsy!rab

		Bob Pendleton
-- 
Bob Pendleton @ Evans & Sutherland
UUCP Address:  {decvax,ucbvax,ihnp4,allegra}!decwrl!esunix!bpendlet
Alternate:     {ihnp4,seismo}!utah-cs!utah-gr!uplherc!esunix!bpendlet
        I am solely responsible for what I say.