Joel Emer

November 28, 2005

6.823, L21-1

VLIW/EPIC: Statically Scheduled ILP

Joel Emer

Computer Science & Artificial Intelligence Laboratory

Massachusetts Institute of Technology

Based on the material prepared by

Krste Asanovic and Arvind

 Joel Emer
November 28, 2005
6.823, L21-2

Little’s Law

Parallelism = Throughput * Latency

or

N = T ×
L
Throughput per Cycle

One Operation
Latency in Cycles
 Joel Emer
November 28, 2005
6.823, L21-3

Example Pipelined ILP Machine

Max Throughput, Six Instructions per Cycle

One Pipeline Stage

Latency Two Integer Units,
in Single Cycle Latency
Cycles
Two Load/Store Units,
Three Cycle Latency
Two Floating-Point Units,
Four Cycle Latency

• How much instruction-level parallelism (ILP)

required to keep machine pipelines busy?

(2x1 + 2x3 + 2x4) 2 2

T =6 L= =2 N = 6 × 2 = 16
6 3 3
 Joel Emer
November 28, 2005
6.823, L21-4

Superscalar Control Logic Scaling

Issue Width W

Issue Group

Previously
Issued Lifetime L

Instructions

• Each issued instructions must make interlock checks against

W*L instructions, i.e., growth in interlocks ∝ W*(W*L)
• For in-order machines, L is related to pipeline latencies
• For out-of-order machines, L also includes time spent in
instruction buffers (instruction window or ROB)
• As W increases, larger instruction window is needed to find
enough parallelism to keep machine busy => greater L
=> Out-of-order control logic grows faster than W2 (~W3)
 Joel Emer
November 28, 2005

Out-of-Order Control Complexity:

6.823, L21-5

MIPS R10000

Control
Logic

[ SGI/MIPS
Technologies
Inc., 1995 ]
 Joel Emer

Sequential ISA Bottleneck

November 28, 2005
6.823, L21-6

Sequential Superscalar compiler Sequential

source code machine code
a = foo(b);
for (i=0, i<

Find independent Schedule

operations operations

Superscalar processor

Check instruction Schedule

dependencies execution
 Joel Emer
November 28, 2005
6.823, L21-7

VLIW: Very Long Instruction Word

Int Op 1 Int Op 2 Mem Op 1 Mem Op 2 FP Op 1 FP Op 2

Two Integer Units,

Single Cycle Latency

Two Load/Store Units,

Three Cycle Latency Two Floating-Point Units,
Four Cycle Latency

• Multiple operations packed into one instruction

• Each operation slot is for a fixed function
• Constant operation latencies are specified
• Architecture requires guarantee of:
– Parallelism within an instruction => no x-operation RAW check
– No data use before data ready => no data interlocks
 Joel Emer
November 28, 2005
6.823, L21-8

VLIW Compiler Responsibilities

The compiler:
• Schedules to maximize parallel execution

• Guarantees intra-instruction parallelism

• Schedules to avoid data hazards (no interlocks)

– Typically separates operations with explicit NOPs
 Joel Emer
November 28, 2005
6.823, L21-9

Early VLIW Machines

• FPS AP120B (1976)
– scientific attached array processor
– first commercial wide instruction machine
– hand-coded vector math libraries using software pipelining
and loop unrolling
• Multiflow Trace (1987)

– commercialization of ideas from Fisher’s Yale group including

“trace scheduling”
– available in configurations with 7, 14, or 28

operations/instruction

– 28 operations packed into a 1024-bit instruction word

• Cydrome Cydra-5 (1987)
– 7 operations encoded in 256-bit instruction word
– rotating register file
 Joel Emer
November 28, 2005

Loop Execution 6.823, L21-10

for (i=0; i<N; i++)

Int1 Int 2 M1 M2 FP+ FPx
B[i] = A[i] + C;
loop: add r1 ld
Compile
loop: ld f1, 0(r1)
add r1, 8 fadd
Schedule
fadd f2, f0, f1
sd f2, 0(r2)
add r2 bne sd
add r2, 8
bne r1, r3, loop

How many FP ops/cycle?

1 fadd / 8 cycles = 0.125
 Joel Emer

Loop Unrolling
November 28, 2005
6.823, L21-11

for (i=0; i<N; i++)

B[i] = A[i] + C;
Unroll inner loop to perform 4
iterations at once
for (i=0; i<N; i+=4)
{
B[i] = A[i] + C;
B[i+1] = A[i+1] + C;
B[i+2] = A[i+2] + C;
B[i+3] = A[i+3] + C;
}
Need to handle values of N that are not multiples
of unrolling factor with final cleanup loop
 Joel Emer
November 28, 2005

Scheduling Loop Unrolled Code 6.823, L21-12

Unroll 4 ways
loop: ld f1, 0(r1) Int1 Int 2 M1 M2 FP+ FPx

ld f2, 8(r1)

ld f3, 16(r1) loop:

ld f1
ld f4, 24(r1)
ld f2
add r1, 32
ld f3
fadd f5, f0, f1
add r1 ld f4 fadd f5
fadd f6, f0, f2
Schedule fadd f6
fadd f7, f0, f3
fadd f7
fadd f8, f0, f4
fadd f8
sd f5, 0(r2)
sd f5
sd f6, 8(r2)
sd f6
sd f7, 16(r2)
sd f7
sd f8, 24(r2)

add r2 bne sd f8
add r2, 32

bne r1, r3, loop

How many FLOPS/cycle?

4 fadds / 11 cycles = 0.36
 Joel Emer
November 28, 2005

Software Pipelining
6.823, L21-13

Int1 Int 2 M1 M2 FP+ FPx

Unroll 4 ways first
loop: ld f1, 0(r1)
ld f1
ld f2, 8(r1)
ld f2
ld f3, 16(r1)
ld f3
ld f4, 24(r1)
add r1 ld f4
prolog
add r1, 32
ld f1 fadd f5
fadd f5, f0, f1
ld f2 fadd f6
fadd f6, f0, f2
ld f3 fadd f7
fadd f7, f0, f3
add r1 ld f4 fadd f8
fadd f8, f0, f4
loop: ld f1 sd f5 fadd f5
sd f5, 0(r2)
iterate
ld f2 sd f6 fadd f6
sd f6, 8(r2)
add r2 ld f3 sd f7 fadd f7
sd f7, 16(r2)
add r1 bne ld f4 sd f8 fadd f8
add r2, 32

sd f5 fadd f5
sd f8, -8(r2)

sd f6 fadd f6
bne r1, r3, loop
epilog
add r2 sd f7 fadd f7
bne sd f8 fadd f8
How many FLOPS/cycle?
sd f5
4 fadds / 4 cycles = 1
 Joel Emer

Software Pipelining
November 28, 2005
6.823, L21-14

vs. Loop Unrolling

Loop Unrolled Wind-down overhead
performance

Startup overhead

Loop Iteration
time

Software Pipelined
performance

Loop Iteration
time

Software pipelining pays startup/wind-down

costs only once per loop, not once per iteration
 Joel Emer
November 28, 2005
6.823, L21-15

What if there are no loops?

• Branches limit basic block size

in control-flow intensive
irregular code
Basic block • Difficult to find ILP in
individual basic blocks
 Joel Emer
November 28, 2005
6.823, L21-16

Trace Scheduling [ Fisher,Ellis]

• Pick string of basic blocks, a trace,

that represents most frequent branch
path
• Use profiling feedback or compiler
heuristics to find common branch
paths
• Schedule whole “trace” at once
• Add fixup code to cope with branches
jumping out of trace
 Joel Emer
November 28, 2005
6.823, L21-17

Problems with “Classic” VLIW

• Object-code compatibility
– have to recompile all code for every machine, even for two
machines in same generation
• Object code size
– instruction padding wastes instruction memory/cache
– loop unrolling/software pipelining replicates code
• Scheduling variable latency memory operations

– caches and/or memory bank conflicts impose statically

unpredictable variability
• Knowing branch probabilities
– Profiling requires an significant extra step in build process
• Scheduling for statically unpredictable branches

– optimal schedule varies with branch path

 Joel Emer
November 28, 2005
6.823, L21-18

VLIW Instruction Encoding

Group 1 Group 2 Group 3

• Schemes to reduce effect of unused fields

– Compressed format in memory, expand on I-cache refill

» used in Multiflow Trace
» introduces instruction addressing challenge
– Mark parallel groups

» used in TMS320C6x DSPs, Intel IA-64

– Provide a single-op VLIW instruction

» Cydra-5 UniOp instructions

 Joel Emer
November 28, 2005

Rotating Register Files

6.823, L21-19

Problems: Scheduled loops require lots of registers,

Lots of duplicated code in prolog, epilog
ld r1, ()
add r2, r1, #1 ld r1, ()
st r2, () add r2, r1, #1 ld r1, ()
st r2, () add r2, r1, #1
st r2, ()

ld r1, ()
Prolog
ld r1, () add r2, r1, #1
Loop ld r1, () add r2, r1, #1 st r2, ()
add r2, r1, #1 st r2, ()
Epilog
st r2, ()

Solution: Allocate new set of registers for each loop iteration

 Joel Emer

Rotating Register File

November 28, 2005
6.823, L21-20

P7
P6
RRB=3 P5
P4
P3
P2
R1 + P1
P0
Rotating Register Base (RRB) register points to base of
current register set. Value added on to logical register
specifier to give physical register number. Usually, split
into rotating and non-rotating registers.

ld r1, () dec RRB

Prolog
ld r1, () add r3, r2, #1 dec RRB Loop closing
Loop ld r1, () add r3, r2, #1 st r4, () bloop branch
decrements RRB
add r2, r1, #1 st r4, () dec RRB
Epilog
st r4, () dec RRB
 Joel Emer

Rotating Register File

November 28, 2005
6.823, L21-21

(Previous Loop Example)

Three cycle load latency Four cycle fadd latency
encoded as difference of 3 encoded as difference of 4
in register specifier in register specifier
number (f4 - f1 = 3) number (f9 – f5 = 4)

ld f1, () fadd f5, f4, ... sd f9, () bloop

ld P9, () fadd P13, P12, sd P17, () bloop RRB=8

ld P8, () fadd P12, P11, sd P16, () bloop RRB=7
ld P7, () fadd P11, P10, sd P15, () bloop RRB=6
ld P6, () fadd P10, P9, sd P14, () bloop RRB=5
ld P5, () fadd P9, P8, sd P13, () bloop RRB=4
ld P4, () fadd P8, P7, sd P12, () bloop RRB=3
ld P3, () fadd P7, P6, sd P11, () bloop RRB=2
ld P2, () fadd P6, P5, sd P10, () bloop RRB=1
 Joel Emer
November 28, 2005

Cydra-5:

6.823, L21-22

Memory Latency Register (MLR)

Problem: Loads have variable latency

Solution: Let software choose desired memory latency

• Compiler schedules code for maximum load-use distance

• Software sets MLR to latency that matches code schedule
• Hardware ensures that loads take exactly MLR cycles to

return values into processor pipeline

– Hardware buffers loads that return early

– Hardware stalls processor if loads return late
 Joel Emer
November 28, 2005
6.823, L21-23

Five-minute break to stretch your legs

 Joel Emer
November 28, 2005
6.823, L21-24

Intel EPIC IA-64

• EPIC is the style of architecture (cf. CISC, RISC)

– Explicitly Parallel Instruction Computing

• IA-64 is Intel’s chosen ISA (cf. x86, MIPS)
– IA-64 = Intel Architecture 64-bit
– An object-code compatible VLIW
• Itanium (aka Merced) is first implementation
(cf. 8086)
– First customer shipment expected 1997 (actually 2001)
– McKinley, second implementation shipped in 2002
 Joel Emer
November 28, 2005
6.823, L21-25

IA-64 Instruction Format

Instruction 2 Instruction 1 Instruction 0 Template

128-bit instruction bundle

• Template bits describe grouping of these

instructions with others in adjacent bundles
• Each group contains instructions that can
execute in parallel
bundle j-1 bundle j bundle j+1 bundle j+2

group i-1 group i group i+1 group i+2

 Joel Emer
November 28, 2005
6.823, L21-26

IA-64 Registers

• 128 General Purpose 64-bit Integer Registers

• 128 General Purpose 64/80-bit Floating Point

Registers
• 64 1-bit Predicate Registers

• GPRs rotate to reduce code size for software

pipelined loops
 Joel Emer
November 28, 2005

IA-64 Predicated Execution 6.823, L21-27

Problem: Mispredicted branches limit ILP

Solution: Eliminate hard to predict branches with predicated execution
– Almost all IA-64 instructions can be executed conditionally under predicate
– Instruction becomes NOP if predicate register false

b0: Inst 1 if
Inst 2
br a==b, b2
Inst 1
b1: Inst 3 else Inst 2
Inst 4 p1,p2 <- cmp(a==b)
br b3 Predication (p1) Inst 3 || (p2) Inst 5
(p1) Inst 4 || (p2) Inst 6
b2: Inst 5 Inst 7
then Inst 8
Inst 6

One basic block

b3: Inst 7
Inst 8
Mahlke et al, ISCA95: On average
>50% branches removed
Four basic blocks
 Joel Emer
November 28, 2005
6.823, L21-28

Predicate Software Pipeline Stages

Single VLIW Instruction

(p1) ld r1 (p2) add r3 (p3) st r4 (p1) bloop

Dynamic Execution

(p1) ld r1 (p1) bloop

(p1) ld r1 (p2) add r3 (p1) bloop
(p1) ld r1 (p2) add r3 (p3) st r4 (p1) bloop
(p1) ld r1 (p2) add r3 (p3) st r4 (p1) bloop
(p1) ld r1 (p2) add r3 (p3) st r4 (p1) bloop
(p2) add r3 (p3) st r4 (p1) bloop
(p3) st r4 (p1) bloop

Software pipeline stages turned on by rotating predicate

registers Î Much denser encoding of loops

 Joel Emer
November 28, 2005
6.823, L21-29

Fully Bypassed Datapath

stall PC for JAL, ...

0x4 nop
E M W
IR IR IR
Add
ASrc 31

we
rs1
rs2
A
PC addr D rd1 we
inst IR ws ALU Y addr
wd rd2
Inst GPRs B rdata
Memory Data
Imm Memory R
wdata
Ext wdata
BSrc
MD1 MD2

Where does predication fit in?

 Joel Emer

IA-64 Speculative Execution

November 28, 2005
6.823, L21-30

Problem: Branches restrict compiler code motion

Solution: Speculative operations that don’t cause exceptions
Speculative load
never causes
Inst 1 Load.s r1 exception, but sets
Inst 2 Inst 1 “poison” bit on
br a==b, b2 Inst 2 destination register
br a==b, b2

Load r1
Use r1 Check for exception in
Inst 3 Chk.s r1 original home block
Use r1 jumps to fixup code if
Inst 3
Can’t move load above branch exception detected
because might cause spurious
exception

Particularly useful for scheduling long latency loads early

 Joel Emer

IA-64 Data Speculation

November 28, 2005

6.823, L21-31

Problem: Possible memory hazards limit code scheduling

Solution: Hardware to check pointer hazards

Data speculative load

Inst 1 adds address to
Inst 2 address check table
Store Load.a r1
Inst 1 Store invalidates any
Load r1 Inst 2
matching loads in
Use r1 Store
address check table
Inst 3 Load.c
Use r1
Can’t move load above store Inst 3 Check if load invalid (or
because store might be to same missing), jump to fixup
address code if so

Requires associative hardware in address check table

 Joel Emer
November 28, 2005

Clustered VLIW
6.823, L21-32

• Divide machine into clusters of

Cluster local register files and local
Interconnect functional units
• Lower bandwidth/higher latency
Local Local Cluster interconnect between clusters
Regfile Regfile • Software responsible for
mapping computations to
minimize communication
overhead
• Exists in some superscalar
Memory Interconnect processors, .e.g., Alpha 21264
• Common in commercial
embedded processors, examples
include TI C6x series DSPs, and
Cache/Memory Banks HP Lx processor
 Joel Emer
November 28, 2005
6.823, L21-33

Limits of Static Scheduling

• Unpredictable branches
• Variable memory latency
(unpredictable cache misses)
• Code size explosion
• Compiler complexity

Question:
How applicable are the VLIW-inspired
techniques to traditional RISC/CISC
processor architectures?
 Joel Emer
November 28, 2005
6.823, L21-34

Thank you !