Path: utzoo!attcan!uunet!hsi!mfci!cutler
From: cutler@mfci.UUCP (Ben Cutler)
Newsgroups: comp.arch
Subject: Re: VLIW Architecture
Keywords: VLIW
Message-ID: <1070@m3.mfci.UUCP>
Date: 8 Oct 89 04:16:44 GMT
References: <251FCB3F.12366@maccs.dcss.mcmaster.ca> <1050@m3.mfci.UUCP> <13050@pur-ee.UUCP> <1630@l.cc.purdue.edu> <1989Oct5.025841.2046@esegue.segue.boston.ma.us> <3449@alliant.Alliant.COM> <1068@m3.mfci.UUCP>
Sender: news@mfci.UUCP
Reply-To: cutler@mfci.UUCP (Ben Cutler)
Organization: Multiflow Computer Inc., Branford Ct. 06405
Lines: 8
Summary:
Expires:
Sender:
Followup-To:
Distribution:

Oops, in case it wasn't clear, the sentence reproduced below describes a
fundamental characteristic of VLIWs (and NOT FPS machines), that operations
don't leave values sitting around in hot spots waiting to be trashed or
pushed along someplace else:

    According to Ellis, ''Every value producing operation and every data
    transfer reads its operands from a register bank and delivers its result
    to a register bank.''