ISBN 0-321-19362-8 Chapter 10 Implementing Subprograms –Nested Subprograms –Blocks –Implementing Dynamic Scoping.

Slides:



Advertisements
Similar presentations
CSI 3120, Implementing subprograms, page 1 Implementing subprograms The environment in block-structured languages The structure of the activation stack.
Advertisements

Subprogram Control - Data sharing Mechanisms to exchange data Arguments - data objects sent to a subprogram to be processed. Obtained through  parameters.
1 Chapter 8 – Subroutines and Control Abstractions.
Implementing Subprograms
(1) ICS 313: Programming Language Theory Chapter 10: Implementing Subprograms.
Chapter 10 Implementing Subprograms. Copyright © 2012 Addison- Wesley. All rights reserved. 1-2 Chapter 10 Topics The General Semantics of Calls and Returns.
Chapter 9 Subprogram Control Consider program as a tree- –Each parent calls (transfers control to) child –Parent resumes when child completes –Copy rule.
Louden, Chapter 8 - Control II: Procedures and Environments.
ISBN Chapter 10 Implementing Subprograms.
PLLab, NTHU,Cs2403 Programming Languages Subprogram and its implementation.
1 Storage Registers vs. memory Access to registers is much faster than access to memory Goal: store as much data as possible in registers Limitations/considerations:
ISBN Chapter 10 Implementing Subprograms.
ISBN Chapter 10 Implementing Subprograms.
ISBN Chapter 10 Implementing Subprograms.
Run time vs. Compile time
Semantics of Calls and Returns
PZ09A Programming Language design and Implementation -4th Edition Copyright©Prentice Hall, PZ09A - Activation records Programming Language Design.
Chapter 9: Subprogram Control
ISBN Chapter 10 Implementing Subprograms –Semantics of Calls and Returns –Implementing “Simple” Subprograms –Implementing Subprograms with.
1 CSCI 360 Survey Of Programming Languages 9 – Implementing Subprograms Spring, 2008 Doug L Hoffman, PhD.
Chapter 10 Implementing Subprograms. Copyright © 2007 Addison-Wesley. All rights reserved. 1–2 Semantics of Call and Return The subprogram call and return.
Chapter 7: Runtime Environment –Run time memory organization. We need to use memory to store: –code –static data (global variables) –dynamic data objects.
ISBN Chapter 10 Implementing Subprograms.
Chapter 9 Subprograms Fundamentals of Subprograms
Chapter 10 Implementing Subprograms. Copyright © 2012 Addison-Wesley. All rights reserved.1-2 Chapter 10 Topics The General Semantics of Calls and Returns.
1 Copyright © 1998 by Addison Wesley Longman, Inc. Chapter 9 Def: The subprogram call and return operations of a language are together called its subprogram.
April 23, ICE 1341 – Programming Languages (Lecture #16) In-Young Ko Programming Languages (ICE 1341) Lecture #16 Programming Languages (ICE 1341)
CSC3315 (Spring 2008)1 CSC 3315 Subprograms Hamid Harroud School of Science and Engineering, Akhawayn University
ISBN Chapter 10 Implementing Subprograms.
Implementing Subprograms What actions must take place when subprograms are called and when they terminate? –calling a subprogram has several associated.
A.Alzubair Hassan Abdullah Dept. Computer Sciences Kassala University A.Alzubair Hassan Abdullah Dept. Computer Sciences Kassala University NESTED SUBPROGRAMS.
Subprograms - implementation
Concepts of programming languages Chapter 5 Names, Bindings, and Scopes Lec. 12 Lecturer: Dr. Emad Nabil 1-1.
1 Chapter 10 © 2002 by Addison Wesley Longman, Inc The General Semantics of Calls and Returns - Def: The subprogram call and return operations of.
Chapter 10 Implementing Subprograms. Copyright © 2012 Addison-Wesley. All rights reserved.1-2 Chapter 10 Topics The General Semantics of Calls and Returns.
10-1 Chapter 10: Implementing Subprograms The General Semantics of Calls and Returns Implementing “Simple” Subprograms Implementing Subprograms with Stack-Dynamic.
ISBN Chapter 10 Implementing Subprograms.
Implementing Subprograms
© G. Drew Kessler and William M. Pottenger1 Subroutines, Part 2 CSE 262, Spring 2003.
PZ09A Programming Language design and Implementation -4th Edition Copyright©Prentice Hall, PZ09A - Activation records Programming Language Design.
1 Activation records Programming Language Design and Implementation (4th Edition) by T. Pratt and M. Zelkowitz Prentice Hall, 2001 Section
Subprograms - implementation. Calling a subprogram  transferring control to a subprogram: save conditions in calling program pass parameters allocate.
Chapter Ten: Implementing Subprograms Lesson 10. Implementing?  Previous lesson: parameter passing  In, out, inout  By value  By reference  Passing.
ISBN Chapter 10 Implementing Subprograms.
Chapter 10 Chapter 10 Implementing Subprograms. Implementing Subprograms  The subprogram call and return operations are together called subprogram linkage.
1 Compiler Construction Run-time Environments,. 2 Run-Time Environments (Chapter 7) Continued: Access to No-local Names.
ISBN Chapter 10 Implementing Subprograms.
Code Generation Instruction Selection Higher level instruction -> Low level instruction Register Allocation Which register to assign to hold which items?
Implementing Subprograms
Chapter 10 : Implementing Subprograms
Implementing Subprograms Chapter 10
Implementing Subprograms
Implementing Subprograms
COMPILERS Activation Records
Implementing Subprograms
Implementing Subprograms
Chapter 10: Implementing Subprograms Sangho Ha
Implementing Subprograms
Implementing Subprograms
Implementing Subprograms
PZ09A - Activation records
Implementing Subprograms
Implementing Subprograms
Activation records Programming Language Design and Implementation (4th Edition) by T. Pratt and M. Zelkowitz Prentice Hall, 2001 Section
Activation records Programming Language Design and Implementation (4th Edition) by T. Pratt and M. Zelkowitz Prentice Hall, 2001 Section
Implementing Subprograms
Activation records Programming Language Design and Implementation (4th Edition) by T. Pratt and M. Zelkowitz Prentice Hall, 2001 Section
Activation records Programming Language Design and Implementation (4th Edition) by T. Pratt and M. Zelkowitz Prentice Hall, 2001 Section
Implementing Subprograms
Chapter 10 Def: The subprogram call and return operations of
Presentation transcript:

ISBN Chapter 10 Implementing Subprograms –Nested Subprograms –Blocks –Implementing Dynamic Scoping

Copyright © 2004 Pearson Addison-Wesley. All rights reserved.10-2 Nested Subprograms Some non-C-based static-scoped languages (e.g., Fortran 95, Ada, JavaScript) use stack- dynamic local variables and allow subprograms to be nested Observation: All variables that can be nonlocally accessed reside in some activation record instance in the stack The process of locating a nonlocal reference: 1. Find the correct activation record instance 2. Determine the correct offset within that activation record instance

Copyright © 2004 Pearson Addison-Wesley. All rights reserved.10-3 The Process of Locating a Nonlocal Reference Finding the offset is easy Finding the correct activation record instance: –Static semantic rules guarantee that all nonlocal variables that can be referenced have been allocated in some activation record instance that is on the stack when the reference is made

Copyright © 2004 Pearson Addison-Wesley. All rights reserved.10-4 Nested Subprograms Technique 1 - Static Chains Technique 2 - Displays

Copyright © 2004 Pearson Addison-Wesley. All rights reserved.10-5 Static Chains A static chain is a chain of static links that connects certain activation record instances The static link in an activation record instance for subprogram A points to one of the activation record instances of A's static parent The static chain from an activation record instance connects it to all of its static ancestors

Copyright © 2004 Pearson Addison-Wesley. All rights reserved.10-6 Static Chains (continued) To find the declaration for a reference to a nonlocal variable: –You could chase the static chain until the activation record instance (ARI) that has the variable is found, searching each ARI as it is found, if variable names were stored in the ARI Static_depth is an integer associated with a static scope whose value is the depth of nesting of that scope

Copyright © 2004 Pearson Addison-Wesley. All rights reserved.10-7 Static Chains (continued) main static_depth = 0 A static_depth = 1 B static_depth = 2 C static_depth = 1

Copyright © 2004 Pearson Addison-Wesley. All rights reserved.10-8 Static Chains (continued) The chain_offset or nesting_depth of a nonlocal reference is the difference between the static_depth of the reference and that of the scope where it is declared A reference can be represented by the pair: (chain_offset, local_offset) where local_offset is the offset in the activation record of the variable being referenced

Copyright © 2004 Pearson Addison-Wesley. All rights reserved.10-9 Example Pascal Program program MAIN_2; var X : integer; procedure BIGSUB; var A, B, C : integer; procedure SUB1; var A, D : integer; begin { SUB1 } A := B + C; < end; { SUB1 } procedure SUB2(X : integer); var B, E : integer; procedure SUB3; var C, E : integer; begin { SUB3 } SUB1; E := B + A: < end; { SUB3 } begin { SUB2 } SUB3; A := D + E; < end; { SUB2 } begin { BIGSUB } SUB2(7); end; { BIGSUB } begin BIGSUB; end. { MAIN_2 }

Copyright © 2004 Pearson Addison-Wesley. All rights reserved Stack Contents at Position 1 Static chain MAIN_2 defines BIGSUB BIGSUB defines SUB1 SUB2 SUB2 defines SUB3 Call sequence for MAIN_2 MAIN_2 calls BIGSUB BIGSUB calls SUB2 SUB2 calls SUB3 SUB3 calls SUB1

Copyright © 2004 Pearson Addison-Wesley. All rights reserved Example Pascal Program At position 1 in SUB1 : A - (0, 3) B - (1, 4) C - (1, 5) At position 2 in SUB3 : E - (0, 4) B - (1, 4) A - (2, 3) At position 3 in SUB2 : A - (1, 3) D - an error E - (0, 5)

Copyright © 2004 Pearson Addison-Wesley. All rights reserved Static Chain Maintenance At the call (assume there are no parameters that are subprograms and no pass-by-name parameters: –The activation record instance must be built –The dynamic link is just the old stack top pointer –The static link must point to the most recent ARI of the static parent (in most situations) Two Methods: 1.Search the dynamic chain until the first ARI for the static parent is found--easy, but slow

Copyright © 2004 Pearson Addison-Wesley. All rights reserved Static Chain Maintenance 2. Treat procedure calls and definitions like variable references and definitions (have the compiler compute the nesting depth, or number of enclosing scopes between the caller and the procedure that declared the called procedure; store this nesting depth and send it with the call) –e.g. Look at MAIN_2 and the stack contents. At the call to SUB1 in SUB3, this nesting depth is 1, which is sent to SUB1 with the call. The static link in the new ARI for SUB1 is set to point to the ARI that is pointed to by the second static link in the static chain from the ARI for SUB3

Copyright © 2004 Pearson Addison-Wesley. All rights reserved Evaluation of the Static Chain Method Problems: 1. A nonlocal reference is slow if the number of scopes between the reference and the declaration of the referenced variable is large 2. Time-critical code is difficult, because the costs of nonlocal references are not equal, and can change with code upgrades and fixes

Copyright © 2004 Pearson Addison-Wesley. All rights reserved Displays The idea: Put the static links in a separate stack called a display. The entries in the display are pointers to the ARI's that have the variables in the referencing environment. Represent references as (display_offset, local_offset) where display_offset is the same as chain_offset Mechanics of references: –Use the display_offset to get the pointer into the display to the ARI with the variable –Use the local_offset to get to the variable within the ARI

Copyright © 2004 Pearson Addison-Wesley. All rights reserved Comparing the Static Chain and Display Methods 1. References to locals –Not much difference 2. References to nonlocals –If it is one level away, they are equal –If it is farther away, the display is faster –Display is better for time-critical code, because all nonlocal references cost the same 3. Procedure calls –For one or two levels of depth, static chain is faster –Otherwise, the display is faster 4. Procedure returns –Both have fixed time, but the static chain is slightly faster Overall: Static chain is better, unless the display can be kept in registers

Copyright © 2004 Pearson Addison-Wesley. All rights reserved Blocks Two Methods: 1. Treat blocks as parameterless subprograms –Use activation records 2. Allocate locals on top of the activation record of the subprogram –Must use a different method to access locals –A little more work for the compiler writer

Copyright © 2004 Pearson Addison-Wesley. All rights reserved Implementing Dynamic Scoping 1. Deep Access - nonlocal references are found by searching the activation record instances on the dynamic chain –Length of chain cannot be statically determined –Every activation record instance must have variable names 2. Shallow Access - put all locals in a central place

Copyright © 2004 Pearson Addison-Wesley. All rights reserved Stack Contents for Dynamic-Scoped Program with deep access

Copyright © 2004 Pearson Addison-Wesley. All rights reserved Dynamic Scoping - Shallow Access Methods: a. One stack for each variable name b. Central table with an entry for each variable name