Article View: comp.arch
Article #2644Re: VLIW SPECmarks (?)
From: Andy-Krazy-Glew
Date: Mon, 16 Oct 1989 17:10
Date: Mon, 16 Oct 1989 17:10
73 lines
3408 bytes
3408 bytes
>One of the machines that did quite well* was the Apollo DN10000, which has,
>among other things, multiple instruction issue (superscalar) and a
>"FP multiply and add" instruction. {was this the inspiration for the
>i860 which appeared 2 years later? :-)}
Urghh.... What do you mean by "superscalar"? I understood it, at
first, to mean "parallel dispatch of instructions from an instruction
set with sequential semantics, after first having checked
dependencies". I think it was in N. Jouppi's paper --- but come to
think of it, that paper contrasted superscalar vs. superpipelined, and
did seem to imply things about VLIW style parallel instruction
dispatch.
May I suggest terminology:
*Parallel instruction dispatch*
dispatching more than one instruction per cycle.
May be done:
*With Interlocks*
assuming an underlying serial model
*Without Interlocks*
*Parallel Instruction Execution*
Executing more than one instruction per cycle.
These instructions may be parallel dispatched, or serially
dispatched. Pipelining is a simple example of
parallel instruction execution, although it is more
interesting to consider non-pipelined versions, where
instructions may cross, etc.
Again, may be w/wo interlocks
*Parallel Instruction Semantics*
Imply that several different operations may be specified in the same
instruction. Implies no interlocks. Most of the recent VLIW-style
announcements are in this category.
There are serial versions of each of the above.
Obviously, they may be combined.
Eg. conceivably a TRACE-28 could do parallel dispatch and execution
of a TRACE-7 program, given suitable dependency checks.
Serial instruction dispatch may be combined with parallel instruction
execution. This was, eg., Tomasulo's original algorithm.
It is not unimaginable that the dispatch unit might be clocked faster
than the execution unit, so that a several instruction parcel that can
be executed in parallel, in a single execution unit cycle, might be built
up from a serial instruction set by a serial dispatch unit in overdrive.
There are some interesting tradeoffs here.
Andy "Krazy" Glew, Motorola MCD, aglew@urbana.mcd.mot.com
1101 E. University, Urbana, IL 61801, USA. {uunet!,}uiucuxc!udc!aglew
My opinions are my own; I indicate my company only so that the reader
may account for any possible bias I may have towards our products.
--
Andy "Krazy" Glew, Motorola MCD, aglew@urbana.mcd.mot.com
1101 E. University, Urbana, IL 61801, USA. {uunet!,}uiucuxc!udc!aglew
My opinions are my own; I indicate my company only so that the reader
may account for any possible bias I may have towards our products.
Technical Details
Message-ID:
<AGLEW.89Oct16131056@chant.urbana.mcd.mot.com>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!asuvax!mcdphx!udc!chant!aglewReferences:
<29287@obiwan.mips.COM>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!asuvax!mcdphx!udc!chant!aglew From: aglew@urbana.mcd.mot.com (Andy-Krazy-Glew) Newsgroups: comp.arch Subject: Re: VLIW SPECmarks (?) Message-ID: <AGLEW.89Oct16131056@chant.urbana.mcd.mot.com> Date: 16 Oct 89 17:10:56 GMT References: <29287@obiwan.mips.COM> Sender: aglew@urbana.mcd.mot.com Organization: Work: Motorola MCD, Urbana Design Center; School: University of Illinois at Urbana-Champaign Lines: 73 In-reply-to: mark@mips.COM's message of 11 Oct 89 12:49:54 GMT