CEG3420 Computer Design

1
CEG3420 Computer Design Lecture 4MIPS
Instruction Set

• Philip Leong

2
Instructions

• Language of the Machine
• More primitive than higher level languages e.g.,
  no sophisticated control flow
• Very restrictive e.g., MIPS Arithmetic
  Instructions
• Well be working with the MIPS instruction set
  architecture
• similar to other architectures developed since
  the 1980's
• used by NEC, Nintendo, Silicon Graphics, Sony
• Design goals maximize performance and minimize
  cost, reduce design time

3
MIPS arithmetic

• All instructions have 3 operands
• Operand order is fixed (destination
  first) Example C code A B C MIPS
  code add s0, s1, s2 (associated
  with variables by compiler)

4
MIPS arithmetic

• Design Principle simplicity favors regularity.
  Why?
• Of course this complicates some things... C
  code A B C D E F - A MIPS
  code add t0, s1, s2 add s0, t0,
  s3 sub s4, s5, s0
• Operands must be registers, only 32 registers
  provided
• Design Principle smaller is faster. Why?

5
Registers vs. Memory

• Arithmetic instructions operands must be
  registers, only 32 registers provided
• Compiler associates variables with registers
• What about programs with lots of variables

6
Memory Organization

• Viewed as a large, single-dimension array, with
  an address.
• A memory address is an index into the array
• "Byte addressing" means that the index points to
  a byte of memory.

0
8 bits of data
1
8 bits of data
2
8 bits of data
3
8 bits of data
4
8 bits of data
5
8 bits of data
6
8 bits of data
...
7
Memory Organization

• Bytes are nice, but most data items use larger
  "words"
• For MIPS, a word is 32 bits or 4 bytes.
• 232 bytes with byte addresses from 0 to 232-1
• 230 words with byte addresses 0, 4, 8, ... 232-4
• Words are aligned i.e., what are the least 2
  significant bits of a word address?

0
32 bits of data
4
32 bits of data
Registers hold 32 bits of data
8
32 bits of data
12
32 bits of data
...
8
Instructions

• Load and store instructions
• Example C code A8 h A8 MIPS
  code lw t0, 32(s3) add t0, s2, t0 sw
  t0, 32(s3)
• Store word has destination last
• Remember arithmetic operands are registers, not
  memory!

9
Our First Example

• Can we figure out the code?

swap(int v, int k) int temp temp
vk vk vk1 vk1 temp
swap muli 2, 5, 4 add 2, 4, 2 lw 15,
0(2) lw 16, 4(2) sw 16, 0(2) sw 15,
4(2) jr 31
10
So far weve learned

• MIPS loading words but addressing bytes
  arithmetic on registers only
• Instruction Meaningadd s1, s2, s3 s1
  s2 s3sub s1, s2, s3 s1 s2 s3lw
  s1, 100(s2) s1 Memorys2100 sw s1,
  100(s2) Memorys2100 s1

11
Machine Language

• Instructions, like registers and words of data,
  are also 32 bits long
• Example add t0, s1, s2
• registers have numbers, t09, s117, s218
• Instruction Format 000000 10001 10010 01000 000
  00 100000 op rs rt rd shamt funct
• Can you guess what the field names stand for?

12
Machine Language

• Consider the load-word and store-word
  instructions,
• What would the regularity principle have us do?
• New principle Good design demands a compromise
• Introduce a new type of instruction format
• I-type for data transfer instructions
• other format was R-type for register
• Example lw t0, 32(s2) 35 18 9
  32 op rs rt 16 bit number
• Where's the compromise?

13
Stored Program Concept

• Instructions are bits
• Programs are stored in memory to be read or
  written just like data
• Fetch Execute Cycle
• Instructions are fetched and put into a special
  register
• Bits in the register "control" the subsequent
  actions
• Fetch the next instruction and continue

memory for data, programs, compilers, editors,
etc.
14
Control

• Decision making instructions
• alter the control flow,
• i.e., change the "next" instruction to be
  executed
• MIPS conditional branch instructions bne t0,
  t1, Label beq t0, t1, Label
• Example if (ij) h i j bne s0, s1,
  Label add s3, s0, s1 Label ....

15
Control

• MIPS unconditional branch instructions j label
• Example if (i!j) beq s4, s5, Lab1
  hij add s3, s4, s5 else j Lab2
  hi-j Lab1 sub s3, s4, s5 Lab2 ...
• Can you build a simple for loop?

16
So far

• Instruction Meaningadd s1,s2,s3 s1 s2
  s3sub s1,s2,s3 s1 s2 s3lw
  s1,100(s2) s1 Memorys2100 sw
  s1,100(s2) Memorys2100 s1bne
  s4,s5,L Next instr. is at Label if s4
  s5beq s4,s5,L Next instr. is at Label if s4
  s5j Label Next instr. is at Label
• Formats

R I J
17
Control Flow

• We have beq, bne, what about Branch-if-less-than
  ?
• New instruction if s1 lt s2 then
  t0 1 slt t0, s1, s2 else t0
  0
• Can use this instruction to build "blt s1, s2,
  Label" can now build general control
  structures
• Note that the assembler needs a register to do
  this, there are policy of use conventions for
  registers

2
18
Policy of Use Conventions
19
Constants

• Small constants are used quite frequently (50 of
  operands) e.g., A A 5 B B 1 C
  C - 18
• Solutions? Why not?
• put 'typical constants' in memory and load them.
  
• create hard-wired registers (like zero) for
  constants like one.
• MIPS Instructions addi 29, 29, 4 slti 8,
  18, 10 andi 29, 29, 6 ori 29, 29, 4
• How do we make this work?

3
20
How about larger constants?

• We'd like to be able to load a 32 bit constant
  into a register
• Must use two instructions, new "load upper
  immediate" instruction lui t0,
  1010101010101010
• Then must get the lower order bits right,
  i.e., ori t0, t0, 1010101010101010

1010101010101010
0000000000000000
0000000000000000
1010101010101010
ori
21
Assembly Language vs. Machine Language

• Assembly provides convenient symbolic
  representation
• much easier than writing down numbers
• e.g., destination first
• Machine language is the underlying reality
• e.g., destination is no longer first
• Assembly can provide 'pseudoinstructions'
• e.g., move t0, t1 exists only in Assembly
• would be implemented using add t0,t1,zero
• When considering performance you should count
  real instructions

22
Overview of MIPS

• simple instructions all 32 bits wide
• very structured, no unnecessary baggage
• only three instruction formats
• rely on compiler to achieve performance what
  are the compiler's goals?
• help compiler where we can

op rs rt rd shamt funct
R I J
op rs rt 16 bit address
op 26 bit address
23
Addresses in Branches and Jumps

• Instructions
• bne t4,t5,Label Next instruction is at Label
  if t4 t5
• beq t4,t5,Label Next instruction is at Label
  if t4 t5
• j Label Next instruction is at Label
• Formats
• Addresses are not 32 bits How do we handle
  this with load and store instructions?

op rs rt 16 bit address
I J
op 26 bit address
24
Addresses in Branches

• Instructions
• bne t4,t5,Label Next instruction is at Label if
  t4t5
• beq t4,t5,Label Next instruction is at Label if
  t4t5
• Formats
• Could specify a register (like lw and sw) and add
  it to address
• use Instruction Address Register (PC program
  counter)
• most branches are local (principle of locality)
• Jump instructions just use high order bits of PC
• address boundaries of 256 MB

op rs rt 16 bit address
I
25
MIPS arithmetic instructions

• Instruction Example Meaning Comments
• add add 1,2,3 1 2 3 3 operands
  exception possible
• subtract sub 1,2,3 1 2 3 3 operands
  exception possible
• add immediate addi 1,2,100 1 2 100
  constant exception possible
• add unsigned addu 1,2,3 1 2 3 3
  operands no exceptions
• subtract unsigned subu 1,2,3 1 2 3 3
  operands no exceptions
• add imm. unsign. addiu 1,2,100 1 2 100
  constant no exceptions
• multiply mult 2,3 Hi, Lo 2 x 3 64-bit
  signed product
• multiply unsigned multu2,3 Hi, Lo 2 x
  3 64-bit unsigned product
• divide div 2,3 Lo 2 3, Lo quotient, Hi
  remainder
• Hi 2 mod 3
• divide unsigned divu 2,3 Lo 2
  3, Unsigned quotient remainder
• Hi 2 mod 3
• Move from Hi mfhi 1 1 Hi Used to get copy of
  Hi
• Move from Lo mflo 1 1 Lo Used to get copy of
  Lo

Which add for address arithmetic? Which add for
integers?
26
MIPS logical instructions

• Instruction Example Meaning Comment
• and and 1,2,3 1 2 3 3 reg. operands
  Logical AND
• or or 1,2,3 1 2 3 3 reg. operands
  Logical OR
• xor xor 1,2,3 1 2 ??3 3 reg. operands
  Logical XOR
• nor nor 1,2,3 1 (2 3) 3 reg. operands
  Logical NOR
• and immediate andi 1,2,10 1 2 10 Logical
  AND reg, constant
• or immediate ori 1,2,10 1 2 10 Logical OR
  reg, constant
• xor immediate xori 1, 2,10 1 2
  10 Logical XOR reg, constant
• shift left logical sll 1,2,10 1 2 ltlt
  10 Shift left by constant
• shift right logical srl 1,2,10 1 2 gtgt
  10 Shift right by constant
• shift right arithm. sra 1,2,10 1 2 gtgt
  10 Shift right (sign extend)
• shift left logical sllv 1,2,3 1 2 ltlt 3
  Shift left by variable
• shift right logical srlv 1,2, 3 1 2 gtgt 3
  Shift right by variable
• shift right arithm. srav 1,2, 3 1 2 gtgt 3
  Shift right arith. by variable

27
MIPS data transfer instructions

• Instruction Comment
• SW 500(R4), R3 Store word
• SH 502(R2), R3 Store half
• SB 41(R3), R2 Store byte
• LW R1, 30(R2) Load word
• LH R1, 40(R3) Load halfword
• LHU R1, 40(R3) Load halfword unsigned
• LB R1, 40(R3) Load byte
• LBU R1, 40(R3) Load byte unsigned
• LUI R1, 40 Load Upper Immediate (16 bits shifted
  left by 16)
• Why need LUI?

LUI R5
0000 0000
R5
28
MIPS Compare and Branch (Fixup)

• Compare and Branch
• BEQ rs, rt, offset if Rrs Rrt then
  PC-relative branch
• BNE rs, rt, offset ltgt
• Compare to zero and Branch
• BLEZ rs, offset if Rrs lt 0 then
  PC-relative branch
• BGTZ rs, offset gt
• BLT lt
• BGEZ gt
• BLTZAL rs, offset if Rrs lt 0 then branch
  and link (into R 31)
• BGEZAL gt
• Remaining set of compare and branch take two
  instructions
• Almost all comparisons are against zero

29
MIPS jump, branch, compare instructions

• Instruction Example Meaning
• branch on equal beq 1,2,100 if (1 2) go to
  PC4100 Equal test PC relative branch
• branch on not eq. bne 1,2,100 if (1! 2) go
  to PC4100 Not equal test PC relative
• set on less than slt 1,2,3 if (2 lt 3) 11
  else 10 Compare less than 2s comp.
• set less than imm. slti 1,2,100 if (2 lt 100)
  11 else 10 Compare lt constant 2s comp.
• set less than uns. sltu 1,2,3 if (2 lt 3)
  11 else 10 Compare less than natural
  numbers
• set l. t. imm. uns. sltiu 1,2,100 if (2 lt 100)
  11 else 10 Compare lt constant natural
  numbers
• jump j 10000 go to 10000 Jump to target address
• jump register jr 31 go to 31 For switch,
  procedure return
• jump and link jal 10000 31 PC 4 go to
  10000 For procedure call

30
Signed vs. Unsigned Comparison
Value? 2s comp Unsigned?

• R1 000 0000 0000 0000 0001
• R2 000 0000 0000 0000 0010
• R3 111 1111 1111 1111 1111
• After executing these instructions
• slt r4,r2,r1 if (r2 lt r1) r41 else r40
• slt r5,r3,r1 if (r3 lt r1) r51 else r50
• sltu r6,r2,r1 if (r2 lt r1) r61 else r60
• sltu r7,r3,r1 if (r3 lt r1) r71 else r70
• What are values of registers r4 - r7? Why?
• r4 r5 r6 r7

two
two
two
31
Calls Why Are Stacks So Great?
Stacking of Subroutine Calls Returns and
Environments
A
A CALL B CALL C
C RET
RET
B
A
B
A
B
C
A
B
A
Some machines provide a memory stack as part of
the architecture (e.g., VAX) Sometimes
stacks are implemented via software convention
(e.g., MIPS)
32
Memory Stacks
Useful for stacked environments/subroutine call
return even if operand stack not part of
architecture
Stacks that Grow Up vs. Stacks that Grow Down
0 Little
inf. Big
Next Empty?
Memory Addresses
grows up
grows down
c
b
Last Full?
a
SP
inf. Big
0 Little
How is empty stack represented?
Little --gt Big/Last Full POP Read from
Mem(SP) Decrement SP PUSH
Increment SP Write to Mem(SP)
Little --gt Big/Next Empty POP Decrement
SP Read from Mem(SP) PUSH
Write to Mem(SP) Increment SP
33
Call-Return Linkage Stack Frames
High Mem
ARGS
Reference args and local variables at fixed
(positive) offset from FP
Callee Save Registers
(old FP, RA)
Local Variables
FP
Grows and shrinks during expression evaluation
SP
Low Mem

• Many variations on stacks possible (up/down, last
  pushed / next )
• Block structured languages contain link to
  lexically enclosing frame
• Compilers normally keep scalar variables in
  registers, not memory!

34
MIPS Software conventions for Registers
0 zero constant 0 1 at reserved for
assembler 2 v0 expression evaluation
3 v1 function results 4 a0 arguments 5 a1 6 a2 7
a3 8 t0 temporary caller saves . . . (callee
can clobber) 15 t7
16 s0 callee saves . . . (caller can
clobber) 23 s7 24 t8 temporary
(contd) 25 t9 26 k0 reserved for OS
kernel 27 k1 28 gp Pointer to global
area 29 sp Stack pointer 30 fp frame
pointer 31 ra Return Address (HW)
Plus a 3-deep stack of mode bits.
35
MIPS / GCC Calling Conventions
FP
SP

• fact
• addiu sp, sp, -32
• sw ra, 20(sp)
• sw fp, 16(sp)
• addiu fp, sp, 32
• . . .
• sw a0, 0(fp)
• ...
• lw 31, 20(sp)
• lw fp, 16(sp)
• addiu sp, sp, 32
• jr 31

ra
low address
FP
SP
ra
ra
old FP
FP
SP
ra
old FP
First four arguments passed in registers.
36
To summarize
37
(No Transcript)
38
Other Issues

• Things we are not going to cover support for
  procedures linkers, loaders, memory
  layout stacks, frames, recursion manipulating
  strings and pointers interrupts and
  exceptions system calls and conventions
• Some of these we'll talk about later
• We've focused on architectural issues
• basics of MIPS assembly language and machine code
• well build a processor to execute these
  instructions.

39
Alternative Architectures

• Design alternative
• provide more powerful operations
• goal is to reduce number of instructions executed
• danger is a slower cycle time and/or a higher CPI
• Sometimes referred to as RISC vs. CISC
• virtually all new instruction sets since 1982
  have been RISC
• VAX minimize code size, make assembly language
  easy instructions from 1 to 54 bytes long!
• Well look at PowerPC and 80x86

40
PowerPC

• Indexed addressing
• example lw t1,a0s3 t1Memorya0s3
  
• What do we have to do in MIPS?
• Update addressing
• update a register as part of load (for marching
  through arrays)
• example lwu t0,4(s3) t0Memorys34s3s3
  4
• What do we have to do in MIPS?
• Others
• load multiple/store multiple
• a special counter register bc Loop
  decrement counter, if not 0 goto loop

41
80x86

• 1978 The Intel 8086 is announced (16 bit
  architecture)
• 1980 The 8087 floating point coprocessor is
  added
• 1982 The 80286 increases address space to 24
  bits, instructions
• 1985 The 80386 extends to 32 bits, new
  addressing modes
• 1989-1995 The 80486, Pentium, Pentium Pro add a
  few instructions (mostly designed for higher
  performance)
• 1997 MMX is addedThis history illustrates
  the impact of the golden handcuffs of
  compatibilityadding new features as someone
  might add clothing to a packed bagan
  architecture that is difficult to explain and
  impossible to love

42
A dominant architecture 80x86

• See your textbook for a more detailed description
• Complexity
• Instructions from 1 to 17 bytes long
• one operand must act as both a source and
  destination
• one operand can come from memory
• complex addressing modes e.g., base or scaled
  index with 8 or 32 bit displacement
• Saving grace
• the most frequently used instructions are not too
  difficult to build
• compilers avoid the portions of the architecture
  that are slow
• what the 80x86 lacks in style is made up in
  quantity, making it beautiful from the right
  perspective

43
Summary

• Instruction complexity is only one variable
• lower instruction count vs. higher CPI / lower
  clock rate
• Design Principles
• simplicity favors regularity
• smaller is faster
• good design demands compromise
• make the common case fast
• Instruction set architecture
• a very important abstraction indeed!