UCB CS61C : Machine Structures

Similar documents
Bonus slides. Garcia, Spring 2014 UCB. CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (18)

ú There are CONVENTIONS when calling procedures! Stack main ()! { a(0);! }! void a (int m)! frame" Garcia, Spring 2013 UCB printf() (y==?

CS61C : Machine Structures

And in Review. Register Conventions (2/4) saved. Register Conventions (1/4) Register Conventions (4/4) Register Conventions (3/4) volatile

CS61C Machine Structures. Lecture 12 - MIPS Procedures II & Logical Ops. 2/13/2006 John Wawrzynek. www-inst.eecs.berkeley.

CS61C : Machine Structures

CS61C : Machine Structures

Review. Lecture #9 MIPS Logical & Shift Ops, and Instruction Representation I Logical Operators (1/3) Bitwise Operations

Lecture 7: Procedures

Lecture 7: Procedures and Program Execution Preview

Lecture 6 Decision + Shift + I/O

UCB CS61C : Machine Structures

CS 61C: Great Ideas in Computer Architecture. More MIPS, MIPS Functions

Numbers: positional notation. CS61C Machine Structures. Faux Midterm Review Jaein Jeong Cheng Tien Ee. www-inst.eecs.berkeley.

Inequalities in MIPS (2/4) Inequalities in MIPS (1/4) Inequalities in MIPS (4/4) Inequalities in MIPS (3/4) UCB CS61C : Machine Structures

CS 61c: Great Ideas in Computer Architecture

CS61C : Machine Structures

ECE 15B Computer Organization Spring 2010

Chapter 2. Computer Abstractions and Technology. Lesson 4: MIPS (cont )

CS61CL : Machine Structures

Final 9am instead of 9:30! Your grade will be ed by autograder! Jeremy Huddleston sb $t1 0($s2)!

CS 61C: Great Ideas in Computer Architecture More MIPS, MIPS Functions

Lecture 5: Procedure Calls

EEM 486: Computer Architecture. Lecture 2. MIPS Instruction Set Architecture

I-Format Instructions (3/4) Define fields of the following number of bits each: = 32 bits

CSE Lecture In Class Example Handout

Branch Addressing. Jump Addressing. Target Addressing Example. The University of Adelaide, School of Computer Science 28 September 2015

Computer Science 2500 Computer Organization Rensselaer Polytechnic Institute Spring Topic Notes: MIPS Programming

Computer Architecture Instruction Set Architecture part 2. Mehran Rezaei

Agenda. Strings: C vs. Java. Loading, Storing bytes. Support for Characters and Strings 6/29/2011

ECE 2035 Programming HW/SW Systems Fall problems, 7 pages Exam Two 23 October 2013

comp 180 Lecture 10 Outline of Lecture Procedure calls Saving and restoring registers Summary of MIPS instructions

COMP 303 Computer Architecture Lecture 3. Comp 303 Computer Architecture

Lecture 5: Procedure Calls

Lecture 2. Instructions: Language of the Computer (Chapter 2 of the textbook)

Control Instructions. Computer Organization Architectures for Embedded Computing. Thursday, 26 September Summary

Control Instructions

Instruction Set Architecture part 1 (Introduction) Mehran Rezaei

Do-While Example. In C++ In assembly language. do { z--; while (a == b); z = b; loop: addi $s2, $s2, -1 beq $s0, $s1, loop or $s2, $s1, $zero

MIPS R-format Instructions. Representing Instructions. Hexadecimal. R-format Example. MIPS I-format Example. MIPS I-format Instructions

CS 110 Computer Architecture Lecture 6: More MIPS, MIPS Functions

MIPS Functions and Instruction Formats

UCB CS61C : Machine Structures

CS 110 Computer Architecture MIPS Instruction Formats

Instructions: Assembly Language

X86 Assembly -Procedure II:1

Overview. Introduction to the MIPS ISA. MIPS ISA Overview. Overview (2)

CSE Lecture In Class Example Handout

Computer Architecture

Lectures 5. Announcements: Today: Oops in Strings/pointers (example from last time) Functions in MIPS

Implementing Procedure Calls

MIPS Instruction Reference

UCB CS61C : Machine Structures

Chapter 2. Instructions: Language of the Computer. Adapted by Paulo Lopes

Chapter 2. Instructions:

CENG3420 Lecture 03 Review

CS 61C: Great Ideas in Computer Architecture. MIPS Instruction Formats

MIPS%Assembly% E155%

Computer Architecture. The Language of the Machine

We will study the MIPS assembly language as an exemplar of the concept.

CSCI 402: Computer Architectures. Instructions: Language of the Computer (3) Fengguang Song Department of Computer & Information Science IUPUI.

MIPS Instruction Set Architecture (2)

UCB CS61C : Machine Structures

Review. Lecture #7 MIPS Decisions So Far...

Lecture 5. Announcements: Today: Finish up functions in MIPS

MIPS Instruction Set

Computer Organization and Structure. Bing-Yu Chen National Taiwan University

CS61C : Machine Structures

CS61C : Machine Structures

Chapter 2A Instructions: Language of the Computer

ECE 2035 Programming HW/SW Systems Spring problems, 6 pages Exam Three 10 April 2013

ECE 2035 Programming HW/SW Systems Spring problems, 6 pages Exam Two 11 March Your Name (please print) total

MIPS Programming. A basic rule is: try to be mechanical (that is, don't be "tricky") when you translate high-level code into assembler code.

UCB CS61C : Machine Structures

Reduced Instruction Set Computer (RISC)

Part II Instruction-Set Architecture. Jan Computer Architecture, Instruction-Set Architecture Slide 1

EEM 486: Computer Architecture. Lecture 2. MIPS Instruction Set Architecture

ECE232: Hardware Organization and Design. Computer Organization - Previously covered

Computer Architecture. Chapter 2-2. Instructions: Language of the Computer

Functions in MIPS. Functions in MIPS 1

ECE 2035 A Programming Hw/Sw Systems Spring problems, 8 pages Final Exam 29 April 2015

MIPS Functions and the Runtime Stack

F. Appendix 6 MIPS Instruction Reference

Thomas Polzer Institut für Technische Informatik

Introduction to the MIPS. Lecture for CPSC 5155 Edward Bosworth, Ph.D. Computer Science Department Columbus State University

ENGN1640: Design of Computing Systems Topic 03: Instruction Set Architecture Design

Week 10: Assembly Programming

COMPSCI 313 S Computer Organization. 7 MIPS Instruction Set

Prof. Kavita Bala and Prof. Hakim Weatherspoon CS 3410, Spring 2014 Computer Science Cornell University. See P&H 2.8 and 2.12, and A.

CISC 662 Graduate Computer Architecture. Lecture 4 - ISA MIPS ISA. In a CPU. (vonneumann) Processor Organization

ECE 2035 Programming HW/SW Systems Spring problems, 6 pages Exam One 4 February Your Name (please print clearly)

ECE 2035 Programming HW/SW Systems Fall problems, 6 pages Exam Two 23 October Your Name (please print clearly) Signed.

Instructor: Randy H. Katz hap://inst.eecs.berkeley.edu/~cs61c/fa13. Fall Lecture #7. Warehouse Scale Computer

CS61C : Machine Structures

ECE 2035 Programming Hw/Sw Systems Fall problems, 10 pages Final Exam 9 December 2013

Today. Putting it all together

Anne Bracy CS 3410 Computer Science Cornell University

COMPUTER ORGANIZATION AND DESIGN

CS 61C: Great Ideas in Computer Architecture (Machine Structures) More MIPS Machine Language

Architecture II. Computer Systems Laboratory Sungkyunkwan University

Transcription:

inst.eecs.berkeley.edu/~cs61c UCB CS61C : Machine Structures Lecture 11 Introduction to MIPS Procedures II & Logical Ops Sr Lecturer SOE Dan Garcia 2014-09-24 Students at Dartmouth allowed researchers to silently measure their stress level (via noting their irregular sleep patterns, reduced social activity (calls, and social networking). Two students who exhibited high stress levels were allowed to get incompletes, since the researchers noted their stress was too high. www.newscientist.com/article/mg22329863.300-failing-students-saved-by-stressdetecting-app.html!

Review Functions called with jal, return with jr $ra. The stack is your friend: Use it to save anything you need. Just leave it the way you found it! Instructions we know so far Arithmetic: add, addi, sub, addu, addiu, subu! Memory: lw, sw, lb, sb Decision: beq, bne, slt, slti, sltu, sltiu Unconditional Branches (Jumps): j, jal, jr Registers we know so far ú All of them! ú There are CONVENTIONS when calling procedures! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (2)

The Stack (review) Stack frame includes: ú Return instruction address ú Parameters ú Space for other local variables 0xFFFFFFFF" Stack frames contiguous blocks of memory; stack pointer tells where bottom of stack frame is When procedure ends, stack frame is tossed off the stack; frees memory for future stack frames $sp" frame" frame" frame" frame" CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (3)

Stack Last In, First Out (LIFO) data structure main ()! { a(0);! }! void a (int m)! { b(1);! }! void b (int n)! { c(2);! }! void c (int o)! { d(3);! }! void d (int p)! {! }! Stack Pointer! Stack Pointer! Stack Pointer! Stack Pointer! Stack Pointer! stack! Stack grows down" CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (4)

Who cares about stack management? Pointers in C allow access to deallocated memory, leading to hard-to-find bugs! int *ptr () {!int y;!y = 3;!return &y; } main () { SP" main" ptr() (y==3)"!int *stackaddr,content;!stackaddr = ptr();!content = *stackaddr;!printf("%d", content); /* 3 */!content = *stackaddr;!printf("%d", content); }/*13451514 */! SP" main" SP" main" printf() (y==?)" CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (5)

Memory Management How do we manage memory? Code, Static storage are easy: they never grow or shrink Stack space is also easy: stack frames are created and destroyed in last-in, first-out (LIFO) order Managing the heap is tricky: memory can be allocated / deallocated at any time CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (6)

Heap Management Requirements Want malloc() and free() to run quickly. Want minimal memory overhead Want to avoid fragmentation* when most of our free memory is in many small chunks ú In this case, we might have many free bytes but not be able to satisfy a large request since the free bytes are not contiguous in memory. * This is technically called external fragmention" CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (7)

Heap Management An example ú Request R1 for 100 bytes ú Request R2 for 1 byte ú Memory from R1 is freed ú Request R3 for 50 bytes R2 (1 byte)" R1 (100 bytes)" CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (8)

Heap Management An example ú Request R1 for 100 bytes ú Request R2 for 1 byte ú Memory from R1 is freed Memory has become fragmented! We have to keep track of the two freespace regions ú Request R3 for 50 bytes We have to search the data structures holding the freespace to find one that will fit! Choice here... CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (9) R2 (1 byte)" R3?" R3?"

Administrivia Project update ú Quick Peer Instruction question: how are you doing the project (1b)? a) [0, 20%) done b) [20, 40%) done c) [40, 60%) done d) [60, 80%) done e) [80, 100%] done TAs, anything? CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (10)

Register Conventions (1/4) CalleR: the calling function CalleE: the function being called When callee returns from executing, the caller needs to know which registers may have changed and which are guaranteed to be unchanged. Register Conventions: A set of generally accepted rules as to which registers will be unchanged after a procedure call (jal) and which may be changed. CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (11)

Register Conventions (2/4) saved $0: No Change. Always 0. $s0-$s7: Restore if you change. Very important, that s why they re called saved registers. If the callee changes these in any way, it must restore the original values before returning. $sp: Restore if you change. The stack pointer must point to the same place before and after the jal call, or else the caller won t be able to restore values from the stack. HINT -- All saved registers start with S! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (12)

Register Conventions (2/4) volatile $ra: Can Change. The jal call itself will change this register. Caller needs to save on stack if nested call. $v0-$v1: Can Change. These will contain the new returned values. $a0-$a3: Can change. These are volatile argument registers. Caller needs to save if they are needed after the call. $t0-$t9: Can change. That s why they re called temporary: any procedure may change them at any time. Caller needs to save if they ll need them afterwards. CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (13)

Register Conventions (4/4) What do these conventions mean? ú If function R calls function E, then function R must save any temporary registers that it may be using onto the stack before making a jal call. ú Function E must save any S (saved) registers it intends to use before garbling up their values, and restore them after done garbling Remember: caller/callee need to save only temporary/saved registers they are using, not all registers. CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (14)

Peer Instruction r:... # R/W $s0,$v0,$t0,$a0,$sp,$ra,mem... ### PUSH REGISTER(S) TO STACK? jal e # Call e... # R/W $s0,$v0,$t0,$a0,$sp,$ra,mem jr $ra # Return to caller of r e:... # R/W $s0,$v0,$t0,$a0,$sp,$ra,mem jr $ra # Return to r! What does r have to push on the stack before jal e? a) 1 of ($s0,$sp,$v0,$t0,$a0,$ra) b) 2 of ($s0,$sp,$v0,$t0,$a0,$ra) c) 3 of ($s0,$sp,$v0,$t0,$a0,$ra) d) 4 of ($s0,$sp,$v0,$t0,$a0,$ra) e) 5 of ($s0,$sp,$v0,$t0,$a0,$ra)! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (15)

Peer Instruction Answer r:... # R/W $s0,$v0,$t0,$a0,$sp,$ra,mem... ### PUSH REGISTER(S) TO STACK? jal e # Call e... # R/W $s0,$v0,$t0,$a0,$sp,$ra,mem jr $ra # Return to caller of r e:... # R/W $s0,$v0,$t0,$a0,$sp,$ra,mem jr $ra # Return to r! What does r have to push on the stack before jal e? Saved Volatile! -- need to push a) 1 of ($s0,$sp,$v0,$t0,$a0,$ra) b) 2 of ($s0,$sp,$v0,$t0,$a0,$ra) c) 3 of ($s0,$sp,$v0,$t0,$a0,$ra) d) 4 of ($s0,$sp,$v0,$t0,$a0,$ra) e) 5 of ($s0,$sp,$v0,$t0,$a0,$ra)! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (16)

And in Conclusion Register Conventions: Each register has a purpose and limits to its usage. Learn these and follow them, even if you re writing all the code yourself. Logical and Shift Instructions ú Operate on bits individually, unlike arithmetic, which operate on entire word. ú Use to isolate fields, either by masking or by shifting back and forth. ú Use shift left logical, sll,for multiplication by powers of 2 ú Use shift right logical, srl,for division by powers of 2 of unsigned numbers (unsigned int) ú Use shift right arithmetic, sra,for division by powers of 2 of signed numbers (int) New Instructions: and, andi, or, ori, sll, srl, sra! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (17)

Bonus slides These are extra slides that used to be included in lecture notes, but have been moved to this, the bonus area to serve as a supplement. The slides will appear in the order they would have in the normal presentation CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (18)

Bitwise Operations So far, we ve done arithmetic (add, sub,addi), mem access (lw and sw), & branches and jumps. All of these instructions view contents of register as a single quantity (e.g., signed or unsigned int) New Perspective: View register as 32 raw bits rather than as a single 32-bit number ú Since registers are composed of 32 bits, wish to access individual bits (or groups of bits) rather than the whole. Introduce two new classes of instructions ú Logical & Shift Ops CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (19)

Logical Operators (1/3) Two basic logical operators: ú AND: outputs 1 only if all inputs are 1 ú OR: outputs 1 if at least one input is 1 Truth Table: standard table listing all possible combinations of inputs and resultant output a! b! a AND b! a OR b! 0! 0! 0! 0! 0! 1! 0! 1! 1! 0! 0! 1! 1! 1! 1! 1! a! a AND b! a OR b! =! 0! 0! b! 1! b! 1! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (20)

Logical Operators (2/3) Logical Instruction Syntax: 1 2,3,4 ú where 1) operation name 2) register that will receive value 3) first operand (register) 4) second operand (register) or immediate (numerical constant) In general, can define them to accept > 2 inputs, but in the case of MIPS assembly, these accept exactly 2 inputs and produce 1 output ú Again, rigid syntax, simpler hardware CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (21)

Logical Operators (3/3) Instruction Names: ú and, or: Both of these expect the third argument to be a register ú andi, ori: Both of these expect the third argument to be an immediate MIPS Logical Operators are all bitwise, meaning that bit 0 of the output is produced by the respective bit 0 s of the inputs, bit 1 by the bit 1 s, etc. ú C: Bitwise AND is & (e.g., z = x & y;) ú C: Bitwise OR is (e.g., z = x y;) CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (22)

Uses for Logical Operators (1/3) Note that anding a bit with 0 produces a 0 at the output while anding a bit with 1 produces the original bit. This can be used to create a mask. ú Example: 1011 0110 1010 0100 0011 1101 1001 1010!!!0000 0000 0000 0000 0000 1111 1111 1111! mask: ú The result of anding these: 0000 0000 0000 0000 0000 1101 1001 1010! mask last 12 bits CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (23)

Uses for Logical Operators (2/3) The second bitstring in the example is called a mask. It is used to isolate the rightmost 12 bits of the first bitstring by masking out the rest of the string (e.g. setting to all 0s). Thus, the and operator can be used to set certain portions of a bitstring to 0s, while leaving the rest alone. ú In particular, if the first bitstring in the above example were in $t0, then the following instruction would mask it: andi! $t0,$t0,0xfff! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (24)

Uses for Logical Operators (3/3) Similarly, note that oring a bit with 1 produces a 1 at the output while oring a bit with 0 produces the original bit. Often used to force certain bits to 1s. ú For example, if $t0 contains 0x12345678, then after this instruction: ori!$t0, $t0, 0xFFFF! $t0 will contain 0x1234FFFF (i.e., the high-order 16 bits are untouched, while the low-order 16 bits are forced to 1s). CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (25)

Example: Fibonacci Numbers 1/8 The Fibonacci numbers are defined as follows: F(n) = F(n 1) + F(n 2), F(0) and F(1) are defined to be 1 In scheme, this could be written: (define (Fib n) (cond!((= n 0) 1) ((= n 1) 1) (else (+!(Fib (- n 1)) (Fib (- n 2)))))! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (26)

Example: Fibonacci Numbers 2/8 Rewriting this in C we have: int fib(int n) {!!!! if(n == 0) { return 1; }!! if(n == 1) { return 1; }!! return (fib(n - 1) + fib(n - 2));! }! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (27)

Example: Fibonacci Numbers 3/8 Now, let s translate this to MIPS! You will need space for three words on the stack The function will use one $s register, $s0! Write the Prologue: fib:! addi $sp, $sp, -12!# Space for three words! sw $ra, 8($sp)!!# Save return address! sw $s0, 4($sp)!!# Save s0! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (28)

Example: Fibonacci Numbers 4/8 Now write the Epilogue: fin:! lw $s0, 4($sp)! lw $ra, 8($sp)! addi $sp, $sp, 12! jr $ra! # Restore $s0 # Restore return address # Pop the stack frame # Return to caller CS61C L12 Introduction to MIPS : Procedures II & Logical Ops (29) Garcia, Spring 2010 UCB

Example: Fibonacci Numbers 5/8 Finally, write the body. The C code is below. Start by translating the lines indicated in the comments int fib(int n) {!!!! if(n == 0) { return 1; } /*Translate Me!*/ if(n == 1) { return 1; } /*Translate Me!*/ return (fib(n - 1) + fib(n - 2)); }! addi!$v0, $zero, 1! beq!$a0, $zero, fin! addi $t0, $zero, 1! beq!$a0, $t0, fin! # $v0 = 1 # # $t0 = 1 # Continued on next slide...! CS61C L12 Introduction to MIPS : Procedures II & Logical Ops (30) Garcia, Spring 2010 UCB

Example: Fibonacci Numbers 6/8 Almost there, but be careful, this part is tricky! int fib(int n) {... return (fib(n - 1) + fib(n - 2)); }! addi $a0, $a0, -1! sw $a0, 0($sp)! jal fib! lw $a0, 0($sp)! addi $a0, $a0, -1! # $a0 = n - 1 # Need $a0 after jal # fib(n - 1) # restore $a0 # $a0 = n - 2 CS61C L12 Introduction to MIPS : Procedures II & Logical Ops (31) Garcia, Spring 2010 UCB

Example: Fibonacci Numbers 7/8 Remember that $v0 is caller saved! int fib(int n) {... return (fib(n - 1) + fib(n - 2)); }! add $s0, $v0, $zero! jal fib! add $v0, $v0, $s0! # Place fib(n 1) # somewhere it won t get # clobbered # fib(n - 2) # $v0 = fib(n-1) + fib(n-2) To the epilogue and beyond...! CS61C L12 Introduction to MIPS : Procedures II & Logical Ops (32) Garcia, Spring 2010 UCB

Example: Fibonacci Numbers 8/8 Here s the complete code for reference: fib:!addi $sp, $sp, -12!!!sw $ra, 8($sp)!!!sw $s0, 4($sp)!!!addi $v0, $zero, 1!!!beq $a0, $zero, fin!!!addi $t0, $zero, 1!!!beq $a0, $t0, fin!!!addi $a0, $a0, -1!!!sw $a0, 0($sp)!!!jal fib!!!lw $a0, 0($sp)!!!addi $a0, $a0, -1!!!add $s0, $v0, $zero!!!jal fib!!!add $v0, $v0, $s0! fin:!lw $s0, 4($sp)!!!lw $ra, 8($sp)!!!addi $sp, $sp, 12!!!jr $ra! CS61C L12 Introduction to MIPS : Procedures II & Logical Ops (33) Garcia, Spring 2010 UCB

Bonus Example: Compile This (1/5) main() { int i,j,k,m; /* i-m:$s0-$s3 */... i = mult(j,k);... m = mult(i,i);...! }! int mult (int mcand, int mlier){ int product;! product = 0; while (mlier > 0) { product += mcand; mlier -= 1; } return product; }! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (34)

Bonus Example: Compile This (2/5) start:!...! add $a0,$s1,$0!!# arg0 = j add $a1,$s2,$0!!# arg1 = k jal mult!!!# call mult add $s0,$v0,$0!!# i = mult()...! add $a0,$s0,$0!!# arg0 = i add $a1,$s0,$0!!# arg1 = i jal mult!!!# call mult add $s3,$v0,$0!...!! j exit! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (35)!# m = mult() main() { int i,j,k,m; /* i-m:$s0-$s3 */... i = mult(j,k);... m = mult(i,i);... }!

Bonus Example: Compile This (3/5) Notes: ú main function ends with a jump to exit, not jr $ra, so there s no need to save $ra onto stack ú all variables used in main function are saved registers, so there s no need to save these onto stack CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (36)

Bonus Example: Compile This (4/5) mult:!!!!!!!! Loop:!add $t0,$0,$0!# prod=0 slt $t1,$0,$a1 # mlr > 0? beq $t1,$0,fin # no=>fin add $t0,$t0,$a0 # prod+=mc addi $a1,$a1,-1 # mlr-=1 j Loop # goto Loop! Fin: add $v0,$t0,$0 # $v0=prod jr $ra # return! int mult (int mcand, int mlier){ int product = 0; while (mlier > 0) { product += mcand; mlier -= 1; } return product; }! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (37)

Bonus Example: Compile This (5/5) Notes: ú no jal calls are made from mult and we don t use any saved registers, so we don t need to save anything onto stack ú temp registers are used for intermediate calculations (could have used s registers, but would have to save the caller s on the stack.) ú $a1 is modified directly (instead of copying into a temp register) since we are free to change it ú result is put into $v0 before returning (could also have modified $v0 directly) CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (38)

Parents leaving for weekend analogy (1/5) Parents (main) leaving for weekend They (caller) give keys to the house to kid (callee) with the rules (calling conventions): ú You can trash the temporary room(s), like the den and basement (registers) if you want, we don t care about it ú BUT you d better leave the rooms (registers) that we want to save for the guests untouched. these rooms better look the same when we return! Who hasn t heard this in their life? CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (39)

Parents leaving for weekend analogy (2/5) Kid now owns rooms (registers) Kid wants to use the saved rooms for a wild, wild party (computation) What does kid (callee) do? ú Kid takes what was in these rooms and puts them in the garage (memory) ú Kid throws the party, trashes everything (except garage, who ever goes in there?) ú Kid restores the rooms the parents wanted saved after the party by replacing the items from the garage (memory) back into those saved rooms CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (40)

Parents leaving for weekend analogy (3/5) Same scenario, except before parents return and kid replaces saved rooms Kid (callee) has left valuable stuff (data) all over. ú Kid s friend (another callee) wants the house for a party when the kid is away ú Kid knows that friend might trash the place destroying valuable stuff! ú Kid remembers rule parents taught and now becomes the heavy (caller), instructing friend (callee) on good rules (conventions) of house. CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (41)

Parents leaving for weekend analogy (4/5) If kid had data in temporary rooms (which were going to be trashed), there are three options: ú Move items directly to garage (memory) ú Move items to saved rooms whose contents have already been moved to the garage (memory) ú Optimize lifestyle (code) so that the amount you ve got to shlep stuff back and forth from garage (memory) is minimized. Mantra: Minimize register footprint Otherwise: Dude, where s my data?! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (42)

Parents leaving for weekend analogy (5/5) Friend now owns rooms (registers) Friend wants to use the saved rooms for a wild, wild party (computation) What does friend (callee) do? ú Friend takes what was in these rooms and puts them in the garage (memory) ú Friend throws the party, trashes everything (except garage) ú Friend restores the rooms the kid wanted saved after the party by replacing the items from the garage (memory) back into those saved rooms CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (43)

Shift Instructions (review) (1/4) Move (shift) all the bits in a word to the left or right by a number of bits. ú Example: shift right by 8 bits 0001 0010 0011 0100 0101 0110 0111 1000! 0000 0000 0001 0010 0011 0100 0101 0110! Example: shift left by 8 bits 0001 0010 0011 0100 0101 0110 0111 1000! 0011 0100 0101 0110 0111 1000 0000 0000! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (44)

Shift Instructions (2/4) Shift Instruction Syntax: 1 2,3,4 where 1) operation name 2) register that will receive value 3) first operand (register) 4) shift amount (constant < 32) MIPS shift instructions: 1. sll (shift left logical): shifts left and fills emptied bits with 0s 2. srl (shift right logical): shifts right and fills emptied bits with 0s 3. sra (shift right arithmetic): shifts right and fills emptied bits by sign extending CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (45)

Shift Instructions (3/4) Example: shift right arithmetic by 8 bits 0001 0010 0011 0100 0101 0110 0111 1000! 0000 0000 0001 0010 0011 0100 0101 0110! Example: shift right arithmetic by 8 bits 1001 0010 0011 0100 0101 0110 0111 1000! 1111 1111 1001 0010 0011 0100 0101 0110! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (46)

Shift Instructions (4/4) Since shifting may be faster than multiplication, a good compiler usually notices when C code multiplies by a power of 2 and compiles it to a shift instruction: a *= 8; (in C) would compile to: sll $s0,$s0,3 (in MIPS) Likewise, shift right to divide by powers of 2 (rounds towards - ) ú remember to use sra! CS61C L11 Introduction to MIPS : Procedures II & Logical Ops (47)