1 / 21

10/6: Lecture Topics

10/6: Lecture Topics. Procedure call Calling conventions The stack Preservation conventions Nested procedure call. Calling Conventions. Sequence of steps to follow when calling a procedure Makes sure: arguments are passed in flow of control from caller to callee and back

asuggs
Télécharger la présentation

10/6: Lecture Topics

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 10/6: Lecture Topics • Procedure call • Calling conventions • The stack • Preservation conventions • Nested procedure call

  2. Calling Conventions • Sequence of steps to follow when calling a procedure • Makes sure: • arguments are passed in • flow of control from caller to callee and back • return values passed back out • no unexpected side effects

  3. Calling Conventions • Mostly governed by the compiler • We’ll see a MIPS calling convention • Not the only way to do it, even on MIPS • Most important: be consistent • Procedure call is one of the most unpleasant things about writing assembly for RISC architectures

  4. A MIPS Calling Convention 1. Place parameters where the procedure can get them 2. Transfer control to the procedure 3. Get the storage needed for the procedure 4. Do the work 5. Place the return value where the calling code can get it 6. Return control to the point of origin

  5. Step 1: Parameter Passing • The first four parameters are easy - use registers $a0, $a1, $a2, and $a3 • You’ve seen this already • What if there are more than four parameters?

  6. Step 2: Transfer Control • Getting from caller to callee is easy -- just jump to the address of the procedure • Need to leave a way to get back again • Special register: $ra (for return address) • Special instruction: jal

  7. Jump and Link Calling code Procedure proc: add .. jal proc

  8. Step 3: Acquire Storage • What storage do we need? • Registers • Other local variables • Where do we get the storage? • From the stack

  9. Refining Program Layout Address 0 Reserved 0x00400000 Program instructions Text 0x10000000 Static data Global variables 0x10008000 Dynamic data heap Local variables, saved registers Stack 0x7fffffff

  10. Saving Registers on the Stack Low address $sp $s2 $s1 $s0 $sp $sp Before During After High address

  11. Assembly for Saving Registers • We want to save $s0, $s1, and $s2 on the stack sub $sp, $sp, 12 # make room for 3 words sw $s0, # store $s0 sw $s1, # store $s1 sw $s2, # store $s2

  12. Step 4: Do the work • We called the procedure so that it could do some work for us • Now is the time for it to do that work • Resources available: • Registers freed up by Step 3 • All temporary registers ($t0-$t9)

  13. Callee-saved vs. Caller-saved • Some registers are the responsibility of the callee • callee-saved registers • $s0-$s7 • Other registers are the responsibility of the caller • caller-saved registers • $t0-$t9

  14. Step 5: Return values • MIPS allows for two return values • Place the results in $v0 and $v1 • You’ve seen this too • What if there are more than two return values?

  15. Step 6: Return control • Because we laid the groundwork in step 2, this is easy • Address of the point of origin + 4 is in register $ra • Just use jr $ra to return

  16. An Example int leaf(int g, int h, int i, int j) { int f; f = (g + h) - (i + j); return f; } Let g, h, i, j be passed in $a0, $a1, $a2, $a3, respectively Let the local variable f be stored in $s0

  17. Compiling the Example leaf: sub $sp, $sp, 4 # room for 1 word sw $s0, 0($sp) # store $s0 add $t0, $a0, $a1 # $t0 = g + h add $t1, $a2, $a3 # $t1 = i + j sub $s0, $t0, $t1 # $s0 = f add $v0, $s0, $zero # copy result lw $s0, 0($sp) # restore $s0 add $sp, $sp, 4 # put $sp back jr $ra # jump back

  18. Nested Procedures • Suppose we have code like this: • Potential problem: the return address gets overwritten main() { foo(); } int foo() { return bar(); } int bar() { return 6; }

  19. A Trail of Bread Crumbs • The registers $s0-$s7 are not the only ones we save on the stack • What can the caller expect to have preserved across procedure calls? • What can the caller expect to have overwritten during procedure calls?

  20. Preservation Conventions Preserved Not Preserved Saved registers: $s0-$s7 Stack pointer register: $sp Return address register: $ra Stack above the stack pointer Temporary registers: $t0-$t9 Argument registers: $a0-$a3 Return value registers: $v0-$v1 Stack below the stack pointer

  21. A Brainteaser in C • What does this program print? Why? #include <stdio.h> int* foo() { int b = 6; return &b; } void bar() { int c = 7; } main() { int *a = foo(); bar(); printf(“The value at a is %d\n”, *a); }

More Related