Path: utzoo!attcan!uunet!husc6!think!ames!amdahl!nsc!stevew
From: stevew@nsc.nsc.com (Steve Wilson)
Newsgroups: comp.arch
Subject: Re: VLIW (was please re-send mail)
Message-ID: <7796@nsc.nsc.com>
Date: 14 Nov 88 21:41:14 GMT
References: <70@armada.UUCP> <28200228@urbsdc> <5087@mit-vax.LCS.MIT.EDU>
Reply-To: stevew@nsc.nsc.com.UUCP (Steve Wilson)
Organization: National Semiconductor, Sunnyvale
Lines: 14

In article <5087@mit-vax.LCS.MIT.EDU> spectre@mit-vax.UUCP (Joseph D. Morrison) writes:
>In article <28200228@urbsdc> aglew@urbsdc.Urbana.Gould.COM writes:
>Naturally, as soon as you do this you will need some mechanism for
>handling the various conflicts that occur when two instructions in the
>pipeline want to use the same register. This is when you can use
>scoreboarding, or whatever you want.
This is where the discussion comes from.  VLIW advocates letting the 
compiler manage both the pipe and register utilization since the 
compiler knows about global resource utilization where a scoreboard 
doesn't.

Steve Wilson 
National Semiconductor
[The above opinion is mine, not that of my employer. ]