02 isa

Instruction Set
Architectures: Talking to
the Machine
1

The Architecture Question
• How do we build computer from contemporary
silicon device technology that executes general-
purpose programs quickly, efﬁciently, and at
reasonable cost?
• i.e. How do we build the computer on your
desk.
2

In the beginning...
• Physical conﬁguration speciﬁes the computation
3
The Difference Engine ENIAC

The Stored Program Computer
• The program is data
• i.e., it is a sequence of numbers that machine interprets
• A very elegant idea
• The same technologies can store and manipulate
programs and data
• Programs can manipulate programs.
4

The Stored Program Computer
• A very simple model
• Several questions
• How are program
represented?
• How do we get
algorithms out of our
brains and into that
representation?
• How does the the
computer interpret a
program?
5
Processor IO
Memory
Data Program

Representing Programs
• We need some basic building blocks -- call them
“instructions”
• What does “execute a program” mean?
• What instructions do we need?
• What should instructions look like?
• Is it enough to just specify the instructions?
• How complex should an instruction be?
6

Program Execution
7
Instruction
Fetch
Instruction
Decode
Operand
Fetch
Execute
Result
Store
Next
Instruction
Read instruction from program storage (mem[PC])
Determine required actions and instruction size
Locate and obtain operand data
Compute result value
Deposit results in storage for later use
Determine successor instruction (i.e. compute next PC).
Usually this mean PC = PC + <instruction size in bytes>
• This is the algorithm for a stored-program
computer
• The Program Counter (PC) is the key

Motivating Code segments
• a = b + c;
• a = b + c + d;
• a = b & c;
• a = b + 4;
• a = b - (c * (d/2) - 4);
• if (a) b = c;
• if (a == 4) b = c;
• while (a != 0) a--;
• a = 0xDEADBEEF;
• a = foo[4];
• foo[4] = a;
• a = foo.bar;
• a = a + b + c + d +... +z;
• a = foo(b); -- next class
8

What instructions do we
need?
• Basic operations are a good choice.
• Motivated by the programs people write.
• Math: Add, subtract, multiply, bit-wise operations
• Control: branches, jumps, and function calls.
• Data access: Load and store.
• The exact set of operations depends on many,
many things
• Application domain, hardware trade-offs, performance,
power, complexity requirements.
• You will see these trade-offs ﬁrst hand in the ISA project
and in 141L.
9

What should instructions look like?
• They will be numbers -- i.e., strings of bits
• It is easiest if they are all the same size, say 32
bits
• We can break up these bits into “ﬁelds” -- like members
in a class or struct.
• This sets some limits
• On the number of different instructions we can have
• On the range of values any ﬁeld of the instruction can
specify
10

Is specifying the instructions sufﬁcient?
• No! We also must what the instructions operate on.
• This is called the “Architectural State” of the
machine.
• Registers -- a few named data values that instructions can
operate on
• Memory -- a much larger array of bytes that is available for
storing values.
• How big is memory? 32 bits or 64 bits of addressing.
• 64 is the standard today for desktops and larger.
• 32 for phones and PDAs
• Possibly fewer for embedded processors
• We also need to specify semantics of function calls
• The “Stack Discipline,” “Calling convention,” or “Application
binary interface (ABI)”.
11

How complex should instructions be?
• More complexity
• More different instruction types are required.
• Increased design and verification costs
• More complex hardware.
• More difficult to use -- What’s the right instruction in this context?
• Less complexity
• Programs will require more instructions -- poor code density
• Programs can be more difficult for humans to understand
• In the limit, decremement-and-branch-if-negative is sufficient
• Imagine trying to decipher programs written using just one
instruction.
• It takes many, many of these instructions to emulate simple
operations.
• Today, what matters most is the compiler
• The Machine must be able to understand program
• A program must be able to decide which instructions to use
12

Big “A” Architecture
• The Architecture is a contract between the
hardware and the software.
• The hardware deﬁnes a set of operations, their
semantics, and rules for their use.
• The software agrees to follow these rules.
• The hardware can implement those rules IN ANYWAY IT
CHOOSES!
• Directly in hardware
• Via a software layer
• Via a trained monkey with a pen and paper.
• This is a classic interface -- they are everywhere
in computer science.
• “Interface,” “Separation of concerns,” “API,” “Standard,”
• For your project you are designing an
Architecture -- not a processor.
13

From Brain to Bits
14
Your brain
Programming
Language (C, C++, Java)
Brain/
Fingers/
SWE
Compiler
Assembly language
Machine code
(i.e., .o ﬁles)
Assembler
Executable
(i.e., .exe ﬁles)
Linker

C Code
15
int i;
int sum = 0;
int j = 4;
for(i = 0; i < 10; i++) {
sum = i * j + sum;
}

In the Compiler
16
Function
decl: i decl: sum = 0 decl: j = 4 Loop
init: i = 0 test: i < 10 inc: i++ Body
statement: =
lhs: sum rhs: expr
sum *
+
j i

In the Compiler
17
sum = 0
j = 4
i = 0
t1 = i * j
sum = sum + t1
i++;
...
i < 10?
false true
Control ﬂow graph
w/high-level
instructions
addi $s0, $zero, 0
addi $s1, $zero, 4
addi $s2, $zero, 0
mult $t0, $s1, $s2
add $s0, $t0
addi $s2, $s2, 1
...
addi $t0, $zero, 10
bge $s2, $t0
true false
Control ﬂow graph
w/real instructions

Out of the Compiler
18
addi $s0, $zero, 0
addi $s1, $zero, 4
addi $s2, $zero, 0
top:
addi $t0, $zero, 10
bge $s2, $t0, after
body:
mult $t0, $s1, $s2
add $s0, $t0
addi $s2, $s2, 1
br top
after:
...
addi $s0, $zero, 0
addi $s1, $zero, 4
addi $s2, $zero, 0
mult $t0, $s1, $s2
add $s0, $t0
addi $s2, $s2, 1
...
addi $t0, $zero, 10
bge $s2, $t0
true false
Assembly language

Labels in the Assembler
19
addi $s0, $zero, 0
addi $s1, $zero, 4
addi $s2, $zero, 0
top:
addi $t0, $zero, 10
bge $s2, $t0, after
mult $t0, $s1, $s2
add $s0, $t0
addi $s2, $s2, 1
br top
after:
...
‘after’ is deﬁned at 0x20
used at 0x10
The value of the immediate for the branch
is 0x20-0x10 = 0x10
‘top’ is deﬁned at 0x0C
used at 0x1C
is 0x0C-0x1C = 0xFFFF0 (i.e., -0x10)

Labels in the Assembler
19
addi $s0, $zero, 0
addi $s1, $zero, 4
addi $s2, $zero, 0
top:
addi $t0, $zero, 10
bge $s2, $t0, after
mult $t0, $s1, $s2
add $s0, $t0
addi $s2, $s2, 1
br top
after:
...
0x00
0x04
0x08
0x0C
0x10
0x14
0x18
0x1C
0x20
‘after’ is deﬁned at 0x20
used at 0x10
is 0x20-0x10 = 0x10
‘top’ is deﬁned at 0x0C
used at 0x1C
is 0x0C-0x1C = 0xFFFF0 (i.e., -0x10)

Assembly Language
20
• “Text section”
• Hold assembly language instructions
• In practice, there can be many of these.
• “Data section”
• Contain deﬁnitions for static data.
• It can contain labels as well.
• The addresses in the data section have no
relation to the addresses in the data section.
• Pseudo instructions
• Convenient shorthand for longer instruction sequences.

.data and pseudo instructions
21
void foo() {
static int a = 0;
a++;
...
}
.data
foo_a:
.word 0
.text
foo:
lda $t0, foo_a
ld $s0, 0($t0)
addi $s0, $s0, 1
st $s0, 0($t0)
after:
...

21
void foo() {
static int a = 0;
a++;
...
}
.data
foo_a:
.word 0
.text
foo:
lda $t0, foo_a
ld $s0, 0($t0)
addi $s0, $s0, 1
st $s0, 0($t0)
after:
...
lda $t0, foo_a
becomes these instructions (this is not assembly language!)
andi $t0, $zero, ((foo_a & 0xff00) >> 16)
sll $t0, $t0, 16
andi $t0, $t0, (foo_a & 0xff)

21
void foo() {
static int a = 0;
a++;
...
}
.data
foo_a:
.word 0
.text
foo:
lda $t0, foo_a
ld $s0, 0($t0)
addi $s0, $s0, 1
st $s0, 0($t0)
after:
...
lda $t0, foo_a
sll $t0, $t0, 16
The assembler computes and inserts these values.

21
void foo() {
static int a = 0;
a++;
...
}
.data
foo_a:
.word 0
.text
foo:
lda $t0, foo_a
ld $s0, 0($t0)
addi $s0, $s0, 1
st $s0, 0($t0)
after:
...
lda $t0, foo_a
sll $t0, $t0, 16
If foo is address 0x0,
where is after?

21
void foo() {
static int a = 0;
a++;
...
}
.data
foo_a:
.word 0
.text
foo:
lda $t0, foo_a
ld $s0, 0($t0)
addi $s0, $s0, 1
st $s0, 0($t0)
after:
...
lda $t0, foo_a
sll $t0, $t0, 16
If foo is address 0x0,
where is after?
0x00
0x0C
0x10
0x14
0x18

ISA Alternatives
• MIPS is a 3-address, RISC ISA
• add rs, rt, rd -- 3 operands
• RISC -- reduced instruction set. Relatively small number
of operation. Very regular encoding. RISC is the “right”
way to build ISAs.
• 2-address
• add r1, r2 --> r1 = r1 + r2
• + few operands, so more bits for each.
• - lots of extra copy instructions
• 1-address
• Accumulator architectures
• add r1 -> acc = acc + rI
22

Stack-based ISA
• A push-down stack holds arguments
• Some instruction manipulate the stack
• push, pop, swap, etc.
• Most instructions operate on the contents of the
stack
• Zero-operand instructions
• add --> t1 = pop; t2 = pop; push t1 + t2;
• Elegant in theory.
• Clumsy in hardware.
• How big is the stack?
• Java byte code is a stack-based ISA
• So is the x86 ﬂoating point ISA
23

24
compute A = X *Y - B * C
• Stack-based ISA
- Processor state: PC, “operand stack”, “Base ptr”
- Push -- Put something from memory onto the stack
- Pop -- take something off the top of the stack
- +, -, *,… -- Replace top two values with the result
X
Y
B
C
A
SP
+4
+8
+12
+16•
•
•
0x1000
Memory
Base ptr (BP)
PC

24
• Stack-based ISA
Push 8(BP)
Push 12(BP)
Mult
Push 0(BP)
Push 4(BP)
Mult
Sub
Store 16(BP)
Pop
X
Y
B
C
A
SP
+4
+8
+12
+16•
•
•
0x1000
Memory
Base ptr (BP)
PC

25
• Stack-based ISA
X
Y
B
C
A
SP
+4
+8
+12
+16
C
•
•
•
0x1000
Memory
Base ptr (BP)
PC

25
• Stack-based ISA
Push 8(BP)
Push 12(BP)
Mult
Push 0(BP)
Push 4(BP)
Mult
Sub
Store 16(BP)
Pop
X
Y
B
C
A
SP
+4
+8
+12
+16
C
•
•
•
0x1000
Memory
Base ptr (BP)
PC

26
• Stack-based ISA
X
Y
B
C
A
SP
+4
+8
+12
+16
C
B
•
•
•
0x1000
Memory
Base ptr (BP)
PC

26
• Stack-based ISA
Push 8(BP)
Push 12(BP)
Mult
Push 0(BP)
Push 4(BP)
Mult
Sub
Store 16(BP)
Pop
X
Y
B
C
A
SP
+4
+8
+12
+16
C
B
•
•
•
0x1000
Memory
Base ptr (BP)
PC

27
• Stack-based ISA
X
Y
B
C
A
SP
+4
+8
+12
+16
B*C
•
•
•
0x1000
Memory
Base ptr (BP)
PC

27
• Stack-based ISA
Push 8(BP)
Push 12(BP)
Mult
Push 0(BP)
Push 4(BP)
Mult
Sub
Store 16(BP)
Pop
X
Y
B
C
A
SP
+4
+8
+12
+16
B*C
•
•
•
0x1000
Memory
Base ptr (BP)
PC

28
• Stack-based ISA
X
Y
B
C
A
SP
+4
+8
+12
+16
B*C
Y
•
•
•
0x1000
Memory
Base ptr (BP)
PC

28
• Stack-based ISA
Push 8(BP)
Push 12(BP)
Mult
Push 0(BP)
Push 4(BP)
Mult
Sub
Store 16(BP)
Pop
X
Y
B
C
A
SP
+4
+8
+12
+16
B*C
Y
•
•
•
0x1000
Memory
Base ptr (BP)
PC

29
• Stack-based ISA
X
Y
B
C
A
SP
+4
+8
+12
+16
X
B*C
Y
•
•
•
0x1000
Memory
Base ptr (BP)
PC

29
• Stack-based ISA
Push 8(BP)
Push 12(BP)
Mult
Push 0(BP)
Push 4(BP)
Mult
Sub
Store 16(BP)
Pop
X
Y
B
C
A
SP
+4
+8
+12
+16
X
B*C
Y
•
•
•
0x1000
Memory
Base ptr (BP)
PC

30
• Stack-based ISA
- Store -- Store the top of the stack
X
Y
B
C
A
SP
+4
+8
+12
+16
B*C
X*Y
•
•
•
0x1000
Memory
Base ptr (BP)
PC

30
• Stack-based ISA
Push 8(BP)
Push 12(BP)
Mult
Push 0(BP)
Push 4(BP)
Mult
Sub
Store 16(BP)
Pop
X
Y
B
C
A
SP
+4
+8
+12
+16
B*C
X*Y
•
•
•
0x1000
Memory
Base ptr (BP)
PC

31
• Stack-based ISA
X
Y
B
C
A
SP
+4
+8
+12
+16
X*Y-B*C
•
•
•
0x1000
Memory
Base ptr (BP)
PC

31
• Stack-based ISA
Push 8(BP)
Push 12(BP)
Mult
Push 0(BP)
Push 4(BP)
Mult
Sub
Store 16(BP)
Pop
X
Y
B
C
A
SP
+4
+8
+12
+16
X*Y-B*C
•
•
•
0x1000
Memory
Base ptr (BP)
PC

32
• Stack-based ISA
X
Y
B
C
A
SP
+4
+8
+12
+16
X*Y-B*C
•
•
•
0x1000
Memory
Base ptr (BP)
PC

32
• Stack-based ISA
Push 8(BP)
Push 12(BP)
Mult
Push 0(BP)
Push 4(BP)
Mult
Sub
Store 16(BP)
Pop
X
Y
B
C
A
SP
+4
+8
+12
+16
X*Y-B*C
•
•
•
0x1000
Memory
Base ptr (BP)
PC

• Functions are an essential feature of modern
languages
• What does a function need?
• Arguments.
• Storage for local variables.
• To return control to the the caller.
• To execute regardless of who called it.
• To call other functions (that call other functions...that
call other functions)
• There are not instructions for this
• It is a contract about how the function behaves
• In particular, how it treats the resources that are shared
between functions -- the registers and memory
33
Supporting Function Calls

Register Discipline
• All registers are the
same, but we assign
them different uses.
34
Name number use saved?
$zero 0 zero n/a
$v0-$v1 2-3 return value no
$a0-$a3 4-7 arguments no
$t0-$t7 8-15 temporaries no
$s0-$7 26-23 saved yes
$t8-$t9 24-25 temporaries no
$gp 26 global ptr yes
$sp 29 stack ptr yes
$fp 30 frame ptr yes
$ra 31 return address yes

Arguments
• How many arguments can
function have?
• unbounded.
• But most functions have just a
few.
• Make the common case fast
• Put the ﬁrst 4 argument in
registers ($a0-$a3).
• Put the rest on the “stack”
35
int Foo(int a, int b, int c, int d, int e) {
...
}
a$a0
b$a1
c$a2
d$a3
0x1DEA$sp
e0x1DEA
Stack (in memory)Register ﬁle

Storage for LocalVariables
• Local variables
go on the stack
too.
36
int Foo(int a, int b, int c, int d, int e) {
int bar[4];
...
}
a$a0
b$a1
c$a2
d$a3
0 x1D EA
$sp
e0 x1D EA
Stack (in memory)Register ﬁle
bar[3 ]
0 x1D EA + 16
$fp
bar[2 ]
bar[1]
bar[0 ]

Returning Control
37
int Foo(int a, ...) {
int bar[4];
...
return bar[0];
}
...
move $a0, $t1
move $a1, $s4
move $a2, $s3
move $a3, $s3
sw $t2, 0($sp)
subi $sp, $sp, 4
jal Foo0xBAD0:
Caller
Callee
...
subi $sp, $sp, 16 // Allocate bar
...
lw $v0, 0($sp)
addi $sp, $sp, 16 // deallocate bar
jr $ra // return
a$a0
b$a1
c$a2
d$a3
0x1DEA
$sp
e0x1DEA
Stack (in memory)
Register ﬁle
bar[3]
0x1DEA + 16
$fp
bar[2]
bar[1]
bar[0]
bar[0]$v0
0xBAD4$ra

Saving Registers
• Some registers are preserved across function calls
• If a function needs a value after the call, it uses one of these
• But it must also preserve the previous contents (so it can
honor its obligation to its caller)
• Push these registers onto the stack.
• See ﬁgure 2.12 in the text.
38

02 isa

More Related Content

What's hot (10)

Viewers also liked (14)

Similar to 02 isa (20)

More from marangburu42 (20)

Recently uploaded (20)

02 isa