ICS312 Set 12 Subroutines: Passing Arguments Using the Stack.

Slides:



Advertisements
Similar presentations
Programming 8086 – Part IV Stacks, Macros
Advertisements

Assembly Language for x86 Processors 6th Edition Chapter 5: Procedures (c) Pearson Education, All rights reserved. You may modify and copy this slide.
There are two types of addressing schemes:
Apr. 12, 2000Systems Architecture I1 Systems Architecture I (CS ) Lecture 6: Branching and Procedures in MIPS* Jeremy R. Johnson Wed. Apr. 12, 2000.
Procedures and Stacks. Outline Stack organization PUSH and POP instructions Defining and Calling procedures.
Subroutines: Passing Arguments Using the Stack. Passing Arguments via the Stack Arguments to a subroutine are pushed onto the stack. The subroutine accesses.
Set 20 Interrupts. INTERRUPTS The Pentium has a mechanism whereby external devices can interrupt it. Devices such as the keyboard, the monitor, hard disks.
Assembly Language for Intel-Based Computers Chapter 8: Advanced Procedures Kip R. Irvine.
IP high IP low IP high IP low BP high BP low IP high IP low BP high BP low FL high FL low CS high CS low IP high IP low _TEXTsegment byte public ‘CODE’
Assembly Language for Intel-Based Computers Chapter 5: Procedures Kip R. Irvine.
Kip Irvine: Assembly Language for Intel-Based Computers Overview Stack Operations (PUSH and POP) Procedures Procedure Parameters Software Interrupts MS-DOS.
Semantics of Calls and Returns
INVOKE Directive The INVOKE directive is a powerful replacement for Intel’s CALL instruction that lets you pass multiple arguments Syntax: INVOKE procedureName.
ICS312 Set 11 Introduction to Subroutines. All the combinations in which a subroutine can be written 1. The subroutine may be: a. Internal or b. External.
ICS312 Set 4 Program Structure. Outline for a SMALL Model Program Note the quiz at the next lecture will be to reproduce this slide.MODEL SMALL.586 ;
Micro-Computer Applications: Procedures & Interrupts Dr. Eng. Amr T. Abdel-Hamid ELECT 707 Fall 2011.
Introduction to Subroutines. All the combinations in which a subroutine can be written 1. The subroutine may be: a. Internal or b. External 2. The type.
Stack Operations LIFO structure (last-in,first-out) –The last value put into the stack is the first value taken out Runtime stack –A memory array that.
ITEC 352 Lecture 18 Functions in Assembly. Functions + Assembly Review Questions? Project due on Friday Exam –Average 76 Methods for functions in assembly.
Assembly Language for Intel-Based Computers, 6 th Edition Chapter 8: Advanced Procedures (c) Pearson Education, All rights reserved. You may.
Chapter 2 Instruction Addressing and Execution. Lesson plan Review some concepts in the first week First assembly program with EMU8086 Related concepts.
Richard P. Paul, SPARC Architecture, Assembly Language Programming, and C Chapter 7 – Subroutines These are lecture notes to accompany the book SPARC Architecture,
ICS312 Set 14 MACROS. Macros The program structure is similar to that for procedures. As for procedure names, macro names represent a group of instructions.
Strings, Procedures and Macros
Lecture 7 A closer look at procedures Dr. Dimitrios S. Nikolopoulos CSL/UIUC.
CEN 226: Computer Organization & Assembly Language :CSC 225 (Lec#9) By Dr. Syed Noman.
Microprocessors The ia32 User Instruction Set Jan 31st, 2002.
L AB 2. P ROGRAM STRUCTURE The assembly language program consist of code, data and stack. Data segment: contains all the variable definition..Data Code.
Writing and using procedures
ITCS 3181 Logic and Computer Systems 2015 B. Wilkinson Slides4-2.ppt Modification date: March 23, Procedures Essential ingredient of high level.
by Richard P. Paul, 2nd edition, 2000.
Subroutines: Passing Arguments Using the Stack. Passing Arguments via the Stack Arguments to a subroutine are pushed onto the stack. The subroutine accesses.
1 The Stack and Procedures Chapter 5. 2 A Process in Virtual Memory  This is how a process is placed into its virtual addressable space  The code is.
Multi-module programming. Requirements of an assembly language module when it is linked with another module PUBLIC directive - it exports to other modules.
Calling Procedures C calling conventions. Outline Procedures Procedure call mechanism Passing parameters Local variable storage C-Style procedures Recursion.
ECE291 Computer Engineering II Lecture 8 Josh Potts University of Illinois at Urbana- Champaign.
Preocedures A closer look at procedures. Outline Procedures Procedure call mechanism Passing parameters Local variable storage C-Style procedures Recursion.
Microprocessors CSE- 341 Dr. Jia Uddin Assistant Professor, CSE, BRAC University Dr. Jia Uddin, CSE, BRAC University.
7-Nov Fall 2001: copyright ©T. Pearce, D. Hutchinson, L. Marshall Oct lecture23-24-hll-interrupts 1 High Level Language vs. Assembly.
Procedures Dr. Hadi Al Saadi Large problems can be divided into smaller tasks to make them more manageable A procedure is the ASM equivalent of a Java.
Chapter 14 Functions.
Assembly language programming
Multi-module programming
Format of Assembly language
COURSE OUTCOMES OF Microprocessor and programming
Instruksi Set Prosesor 8088
Microprocessor and Assembly Language
Microprocessor and Assembly Language
Assembly Language Programming Part 2
(The Stack and Procedures)
Chapter 3 Addressing Modes
Chapter 7 Subroutines Dr. A.P. Preethy
CS 301 Fall 2002 Control Structures
Stack and Subroutines Module M17.1 Section 11.2.
Programming 8086 – Part IV Stacks, Macros
8086 Registers Module M14.2 Sections 9.2, 10.1.
Procedures – Overview Lecture 19 Mon, Mar 28, 2005.
Microprocessor and Assembly Language
EECE.3170 Microprocessor Systems Design I
(The Stack and Procedures)
by Richard P. Paul, 2nd edition, 2000.
EECE.3170 Microprocessor Systems Design I
EECE.3170 Microprocessor Systems Design I
Morgan Kaufmann Publishers Computer Organization and Assembly Language
EECE.3170 Microprocessor Systems Design I
Miscellaneous Topics.
Some Assembly (Part 2) set.html.
(The Stack and Procedures)
Procedures and Macros.
Chapter 14 Functions.
Presentation transcript:

ICS312 Set 12 Subroutines: Passing Arguments Using the Stack

Passing Arguments via the Stack Arguments to a subroutine are pushed onto the stack. The subroutine accesses the arguments from the stack using the Base Pointer (BP) and indirect addressing. Arguments can be passed by value (their values are pushed onto the stack, or by reference (their offsets are pushed onto the stack).

The calling routine used in MAIN3 can be either: To use CALL by Value : PUSH X PUSH Y CALL SUB1 To use CALL by Reference : PUSH OFFSET X PUSH OFFSET Y CALL SUB1

Call by Value Using the Stack Suppose that X and Y are defined in the MAIN file: X DW... Y DW... To call a subroutine CALC to evaluate X - 2Y using call by value:

TITLE MAIN3 (main3.asm) EXTRN CALC: NEAR.MODEL SMALL.STACK 100H.DATA X DW 30 Y DW 40.CODE MAIN3 PROC MOV MOV DS, AX PUSH Y ; call by value PUSH X CALL CALC ; the answer should be returned in AX MOV AX,4C00H INT 21H MAIN3 ENDP END MAIN3

Pay close attention to the following slide (and the one so indicated a few slides on). These are the methods used by all commercial compilers You are expected to know these methods off by heart! You’ll be asked to supply them both in a quiz and in the midterm.

Call by Value Using the Stack(Cont.) TITLE CALC (CALC.ASM - a separate file) PUBLIC CALC.MODEL SMALL.CODE CALC PROC NEAR ;evaluates X - 2Y with result in AX PUSH BP ;save BP MOV BP,SP ;BP points to stack top ; push any registers to be used in the subroutine and ; restored before returning from the subroutine here MOV AX,[BP+4] ;AX has X SUB AX,[BP+6] ;AX = X - Y SUB AX,[BP+6] ;AX = X - 2Y ; pop any registers that were saved in the subroutine here POP BP ;restore BP RET 4 ;pop IP and add 4 bytes to SP CALC ENDP END

Call by Value Using the Stack(Cont.) Stack Representation for NEAR Call by Value in this version of the program: Instruction Stack Contents SP BP (at the end of this code) PUSH Y (Arg1) Y SP -=2 [BP+6] = offset of Y on stack PUSH X (Arg2) X SP -=2 [BP+4] = offset of X on stack CALL CALC Ret Address SP -=2 [BP+2] = RETADDR (IP) PUSH BP BP SP -=2 [BP] = original contents of BP MOV BP, SP BP = SP push regs regs SP -=2/each reg

Call by Value Using the Stack(Cont.) The purpose of using the BP in this way is because it gives a standard way to retrieve arguments from the stack that is not affected by pushing any additional registers or other values within the subroutine. Note: if BP is used for indirect addressing, it is assumed to be referring to an offset in the stack segment (SS). Any other register used for indirect addressing is assumed to be an offset in the data segment (DS).

TITLE CALC (CALC.ASM - a separate file) PUBLIC CALC.MODEL SMALL.CODE CALC PROC NEAR ;evaluates X - 2Y with result in AX PUSH BP ;save BP MOV BP,SP ;BP points to stack top ; push any registers to be used in the subroutine MOV AX, [BP+4] ;AX has X SUB AX, [BP+6] ;AX = X - Y SUB AX, [BP+6] ;AX = X - 2Y ; pop any registers that were saved in the subroutine POP BP ;restore BP RET 4 ;pop IP and add 4 bytes to SP CALC ENDP END

NOTE C assumes that (1)the calling program will fix the stack after the return from a subroutine (2) arguments will be passed using call by value (3) arguments are pushed in reverse order, as shown above. Different compilers use different calling conventions.

Call by Reference Using the Stack Here is another version to demonstrate passing arguments by reference on the stack. TITLE MAIN3 (main3.asm) EXTRN SUB2: NEAR.MODEL SMALL.STACK 100H.DATA X DW 30 Y DW 40

.CODE MAIN3 PROC MOV MOV DS,AX PUSH OFFSET Y ;using call by reference PUSH OFFSET X ;using call by reference CALL CALC ; answer should be in AX MOV AX,4C00H INT 21H MAIN3 ENDP END MAIN3

The following slide (and its continuation) is the other method (call by reference) used by commercial compilers and which you are expected to know off by heart!

Call by Reference Using the Stack TITLE SUB2 (sub2.asm - a separate file) PUBLIC SUB2.MODEL SMALL.CODE SUB2 PROC NEAR ;evaluates X - 2Y, with result in AX PUSH BP ;save BP (and DEC SP) MOV BP,SP ;BP pts to stack top ; push any registers to be used in the subroutine and ; restored before returning from the subroutine here

MOV BX, [BP+4] ;BX has address of X (not its value) MOV AX, [BX] ;AX has the value of X MOV BX, [BP+6] ;BX has address of Y SUB AX, [BX] ;AX = X - Y SUB AX, [BX] ;AX = X - 2Y ;pop any registers that were saved in the subroutine here POP BP ;restore BP RET 4 ;pop IP and add 4 bytes to SP SUB2 ENDP END

Stack Representation for call by reference example Instruction Stack contents SP BP (at end of this code) PUSH AX Y address SP -=2 [BP+6]= Y address PUSH AX X address SP -=2 [BP+4]= X address CALL ADDNOS IP SP -=2 [BP+2] = return addr. offset PUSH BP BP SP -=2 [BP] = orig. contents of BP MOV BP, SP BP = SP PUSH regs regs SP -=2/reg

Example on storing a result in an argument Call SUB(X, Y, Z), Result is to set Z = Y – X Main Program. PUSH OFFSET X PUSH OFFSET Y PUSH OFFSET Z CALL SUB.

Example on storing a result in an argument (Cont.1) Title SUB3.Model Small.586 PUBLIC SUB.CODE SUB PROC NEAR PUSH BP ;Save BP MOV BP, SP PUSH DX ;Save DX PUSH BX ;Save BX MOV BX, [BP+6] ;BX = OFFSET of ADDRESS of Y MOV DX, [BX] ;DX = Y MOV BX, [BP+8] ;BX = OFFSET of ADDRESS of X SUB DX, [BX] ;DX = Y – X

Example on storing a result in an argument (Cont.2) ; to store DX in Z MOV BX, [BP+4] ; puts offset of Z into BX MOV [BX], DX POP BX ; restore original value of BX POP DX POP BP RET 6 SUB ENDP END

FIXING UP THE STACK If the subroutine is to fix up the stack, then it should end up with: RET 2*no. of arguments e.g. if there are 3 arguments, then it should end up with: RET 6 If the calling program is to fix up the stack, then the subroutine should end up with: RET and, assuming that the subroutine is SUB1, the calling program should contain the code: call sub1 add sp, 6 (i.e. 2*no. of arguments)

ILLUSTRATION OF A RECURSIVE PROCEDURE A procedure to evaluate factorial(n) if n = 1 return 1 else return n*factorial(n-1)

factorialproc near push bp mov bp,sp cmp word ptr [bp+4], 1 jg cont mov ax, 1 jmp endup cont:mov bx, [bp+4] dec bx push bx call factorial

imulword ptr [bp+4] endup: pop bp ret 2 factorial endp end

An Example of a Recursive Procedure Employed in Cryptography Definition. The GCD (greatest common denominator) of two numbers a, b is the largest number that divides both a and b. 25

Euler’s Extended Algorithm. For given a, b to find: (a) the GCD d of a, b (b) numbers x and y (positive, negative or zero) such that xa + yb = d (Euler’s original algorithm is just part (a) ) 26

If a = b, then obviously the GCD of (a,b) is a, and we have a*1 + b*0 = a Otherwise, proceed as follows:

Define E(a,b) as a function whose value is the triple (x, y, d) such that d is the GCD of a, b and xa + yb = d. E(a,b) can then be evaluated using the following recursive algorithm: Function E(a, b) where a > b If b = 0 then return (1, 0, a), else evaluate q, r such that a = qb + r and 0 ≤ r < b. Evaluate E(b, r), let result be (X, Y, D) Return (Y, X – qY, D) End function 28

EXAMPLE. To find the GCD d of 75 and 30, and, further to find x, y such that 75x + 30y = d. E(75, 30) = (x 1, y 1, d) to be filled in later 75 = 2* (so q 1 = 2) E(30, 15) = (x 2, y 2, d) to be filled in later 30 = 2* (so q 2 = 2) E(15, 0) = (x 3, y 3, d) = (1, 0, 15). So d = 15. Now x 2 =y 3 =0 and y 2 = x 3 – q 2 y 3 = 1 and x 1 =y 2 =1 and y 1 = x 2 – q 1 y 2 = -2 So d = 15 and 1*75 + (-2)*30 = 15 29

PROOF THAT THE ALGORITHM WORKS (optional) First of all note that since a = qb + r, any number that divides both b and r must also divide a (so it divides both a and b). And since r = a – qb, any number that divides both a and b must also divide r (so it divides both b and r). Thus the largest number that divides both b and r must also be the largest number that divides both a and b i.e. the GCD of a,b = GCD of b,r

The case where b = 0 obviously returns the correct result, since 1*a + 0*0 = a, and a is the GCD of a and 0. If b > 0, and q, r, X, Y, D are as defined in the algorithm, then Xb + Yr = D where D is the GCD of b,r and hence also of a,b Since r = a - qb, this provides Xb + Y(a-qb) = D Giving Ya + (X-qY)b = D 31

Finally note that the algorithm terminates, because the second argument decreases in each successive recursive call. So the sequence of iterations must end up with one in which the second argument is zero 32

Textbook Reading (Jones): Chapter 13 Procedures and High-Level Languages