Lecture 37, Nesting and Continuations

Part of the notes for 22C:196:002 (CS:4908:0002)
by Douglas W. Jones
THE UNIVERSITY OF IOWA Department of Computer Science

That Blasted Stack-Based Architecture

Consider the compilation of this little bit of code, with variables temp and a being local (where local includes, potentially, parameters):

temp = a

If we compile this for the suggested stack architecture that is a model for a potential intermediate code or an interface to the code generator, we might get this:

            -- ///|
            -- ///| @temp |
            -- ///| @temp |  @a   |
            -- ///| @temp |   a   |
            -- ///|

The comments in the above code show the contents of the stack (in symbolic form) before and after each instruction. Pushing adds items to the right. Note that the above uses the notation @temp to mean "the address of temp" while the notation temp is used to indicate the value of that locaiton.

We emphasize, here, the meanings of the instructions:

Push the address of the local variable x on the stack. This is the sum of the frame pointer and the displacement x measured from the frame pointer.
Replace the stack top with the contents of the memory location pointed to by the stack top.
Pop a value off of the stack, and then pop an address off of the stack, and then store that value in the memory location pointed to by the address.

Also note that locations on the stack can themselves be statically allocated as variables in the activation record, since at any point in the code, the displacement of the stack pointer from the frame pointer can be computed as a static constant.

Up-level Addressing

Conside this code:

var a: int32;
procedure b
    var c: int32;
    code c = a;
procedure d
    var e: int32;
    procedure f
       code e = a; a = 1; b;
    if (a = 0) then d;
code a = 0; d;

The problem is, how do we do up-level addressing here. As we noted in Lecture 29, we will rely on an up-link at displacement up in each activation record. How does this get set? Let's look at how the above code is compiled, one step at a time, but first, note that we did not say that the outer level here was global. In order to give the most general answer, we will assume that that code might itself be several levels of nesting in from the global level:

Let us first look at the procedure f above. How does the up pointer in its own activation record get set? This procedure is called from within the recursive procedure d. Therefore, the value of the up pointer in any particular instance of f depends on which instance of d is active at the time of the call.

We solve this by adding an implicit parameter to every procedure and function, the up-link to be used by the called procedure. Thus, we can compile f as follows:

f:  RECEIVE 1, 0, 0
    -- e = a
    PUSHLA up
    ADDI   e -- compute the address up.e
    PUSHLA up
    ADDI   up
    ADDI   a -- compute the address up.up.a
    POP      -- do the assignment
    -- a = 1
    PUSHLA up
    ADDI   up
    ADDI   a -- compute the address up.up.a
    PUSHI  1
    POP      -- do the assignment
    -- b
    PUSHLA up
    ADDI   up
    LOAD     -- compute the address up.up.0, the up link for b
    CALLI  b, 1
    RETURN 1, 0, 0

Note here that we have added a new instruction to our stack architecture:

Add the immediate constant x to the value on the stack top. Here, the value on the stack top is always an address, and x is the displacement of a field of the record pointed to by that address.
CALLI a, b
Generates the calling sequence for a procedure or function at static address a and with b parameters that have already been pushed onto the stack.
RECEIVE a, b, c
Generates the receiving sequence for a procedure or function with one a parameters passed by pushing them on the stack, b local variables and a return value that occupies c words.
RETURN a, b, c
Generates the return sequence for a procedure or function with one a parameters passed by pushing them on the stack, b local variables and a return value that occupies c words. These arguments must match the arguments on the receiving sequence -- depending on details that are not known at this level of abstraction, the arguments might not be needed.

Given the above, which illustrates the general case, we can now write code for the procedure d:

d:  RECEIVE 1, 1, 0
    PUSHLA up
    ADDI   a -- compute the address up.a
    PUSHI  0
    BFALSE eif
    PUSHLA up
    CALLI  d, 1
    PUSHLA 0
    CALLI  f, 1

General Principles

Note in the above, if we are at nesting level i and we reference any object (procedure, function, variable or parameter) declared at level j, where i > j, we always begin by following i – j up links (which requires i – j LOAD operations). In the case of a global variable x, the final instruction is ADDI x to compute the address of that variable, while in the case of a call to a procedure or function p, we then push any additional parameters before calling the function itself.

For calls to local procedures or functions, that is where we are at nesting level i and we reference a procedure or function declared at level i, we simply push a copy of our own frame pointer as the up pointer for the called procedure or function, using PUSHLA 0 (that is, with a displacement of zero).

Passing Procedures and Functions Parameters

As currently defined, Falcon does not support passing procedures and functions as parameters, but it could naturally do so. In that case, the procedure or function parameter must be a two-word quantity consisting of the actual pointer to the procedure or function, plus the pointer to the procedure or function's enclosing block, that is, the up-link for that procedure or function.

At whatever point in the code where the procedure or function parameter is formed by direct reference to the required procedure or function, the up-link can be computed as described above. From that point onward, as the procedure or function parameter is passed and passed on from one place to another in the code, the pair giving the code address and its context is always passed onward as a pair.

Relationship to Methods of Objects

A call to a method of an object operates in a manner identical to the above. The caller must have the ability to address the object. The object itself is the enclosing context for the method, so the caller passes the pointer to the enclosing object as the first parameter to the method. Thus, up-level addressing from methods of objects to the fields of that object is no different from up-level addressing from functions to variables global to those functions.

When an instance of an object is created, the instance must contain an up-pointer to the context in which the object's type is declared. Note that the object's initializer can be considered to be called like a procedure with a funny return sequence that does not deallocate the instance and a funny receiving sequence that allocates the space for the object somewhere other than the stack. Seen this way, the initializer must be passed a pointer to the static context of the type declaraton, and this context may then be used as the up-link for the object itself.


Genuinely global variables may always be statically allocated, so they may always be addresses using static addresses. This requires a new form of push instruction in our stack model:

Push the static address of the global variable x on the stack.

Given this, we can always generate direct references to genuinely global objects, and no object declared at the global level (including activation records for global procedures or functions) needs to have an up-link allocated within it or passed to it.

Furthermore, any procedure or function that does not reference any variables that are global to it but not at the outermost (static) level does not need an up link, nor do calls to that procedure or function need to pass such a link.

Objects that contain no code or methods that address variables global to that object but not at the outermost level do not need to contain up links. Really good compilers can determine these properties and make these allocations.

Connection to Theory

Programming language theorists describe the binding of a block of code to the definitions for the identifiers in that code as a closure. This terminology is frequently used with the lambda calculus; consider this expression:

λa b.a(b)

This is an unclosed expression, with both a and b unbound. In contrast, this expression is described as a closure of the above:

(λa b.a(b))(succ 1)

It is a closure because it provides values for both a and b, allowing lambda substitution to produce this:


Of course, we now have the problem of defining the succ function, although it is worth noting that in significant areas of computer science theory, this is seen as a primitive that is never evaluated. Now consider this expression, a partial closure of our original expression:

λc.(λa b.a(b))(c 1)

This binds b to the value 1, while leaving a undefined, except that it has been renamed c, but that renaming is not significant, since names of formal parameters are meaningless. In sum, the above partial binding is equivalent to this:


The point of this exercise is that, by the time the body of a Falcon subroutine is executed, we must have a complete closure of the body, with every identifier in the body bound to some actual object. This binding involves two separate steps, first, binding the block to its static context, a partial closure, and second, binding the actual parameters to the formal parameters, a step that completes the closure.


Consider this fragment of Falcon code:

exception e;
procedure f
    if (conditiona) f; end;
    if (conditionb) raise e; end;
        if (conditionc) raise e; end;
    handle e

How does this work? First, note that Falcon exceptions must be declared, and the declaration must be visible from both the point where the exception is raised and the point where it is handled. The declaration itself creates a default handler for that exception one that terminates the program ungracefully.

A compiler designed for student use should have a nice default handler, perhaps one that outputs something like unhandled e exception, but the formal semantics of the language does not specify a particular behavior for unhandled exceptions. They are considered to be errors, and the formal semantics only specifies the behavior of correct programs.

All exception handling models share the following basic idea. At the start of the try block, the previous handler for the exception in question is saved (conceptually pushed on a stack), and the new handler is installed. At the end of the try block, the previous handler is restored. On entry to a handler, the previous handler is also restored, so that raising an exception within the handler cannot lead to a loop.

What is an exception? There are two models that are common in different programming languages:

  1. Each exception declaration defines a new object of type exception. To support this, when we compile a try block, we must know which exceptions we are installing handlers for.

  2. There is just one global exception object. Exception identifiers are actually members of an implicit global enumerated type that is extended with new members each time a new exception is declared. The handlers at the end of any try block are, in effect, a case-select construct that selects a handler based on the value selected from the enumeration.

Falcon try blocks do not delcare, up front, which handler is to be installed for that block, and the handlers at the end of the block may include an else handler for all other exceptions other than those named explicitly. These two language design features force us to use the second exception handling model.

Exception Objects

So what is an exception object? At the very minimum, an exception object must obviously record the address of the code for the handler. Otherwise, how could the raise statement possibly transfer control to the handler.

But, the handler runs in the context of some Falcon block, and all Falcon blocks must be presumed to be dynamically allocated, with, at the very least, a frame pointer allowing reference to variables in that block. Therefore, we must also include the correct value for the frame pointer. We could also include a saved stack pointer, but in Falcon, the displacement from the stack pointer to the frame pointer is a constant that can be statically computed at every point in the code. Therefore, if the frame pointer is restored, we can immediately compute the correct stack pointer value and restore the stack pointer that way.

In sum, we can imagine the standard prologue for a Falcon program as including something equivalent to the following declarations, all of which are invisible to the programmer:

    TYPEexception = record var
        handler: MACHINEword;
        frame: MACHINEword;
    ENUMexception = ENUM ( );
var VARexception: TYPEexception;

That is, we have two implicit types, TYPEexception, the type of the single exception variable named here VARexception that is statically allocated and declared globally, and ENUMexception an enumeration type that is, anomalously, initially empty and that has members added to it each time there is a new exception declaraiton.

Actually, there should probably be some predefined exceptions. Consider, for example, RangeError a possible name for the exception raised when a program tries to assign a value to a variable where that value is outside the range of values permitted by the type of that variable. This exception should also apply when the value of an expression is outside the range of values permitted for that expression, for example, when used as an array subscript or as an actual parameter.

Exception Objects

The above provides us with enough information to write code to raise an exception.

Raise the exception e by first placing the value e in a designated special register (see below); the value e must be one of the constants of type ENUMexception. Second, the frame pointer is set to VARexception.frame and the program counter is set to VARexception.handler.

Also note that locations on the stack can themselves be statically allocated as variables in the activation record, since at any point in the code, the displacement of the stack pointer from the frame pointer can be computed as a static constant.


Now, look at how we compile a try-handle statement that was given in the original example.

-- try var SAVEexception: TYPEexception; code SAVEexcepiton = VARexception; -- save the old handler's identity VARexception.handler = HANDLE; VARexception.handler = fp; -- new handler is installed f; if (conditionc) -- raise e; SPECIALregister = e JUMP HANDLE end; -- handle e VARexcepiton = SAVEexception; -- restore the old handler's identity JUMP DONE HANDLE: VARexcepiton = SAVEexception; -- restore the old handler's identity if SPECIALregister = e f; else fp = VARexception.frame; JUMP VARexception.handler end; -- end DONE:

Note three things here: First, the old value of the global VARexcepiton is saved in a local variable SAVEexception. The programmer never explicitly mentions either of these variables, but actual RAM must be allocated for both the global variable and the save location for each and every try. Of course, this local variable may be deallocated as soon as it is used at the start of the first handler following the try block.

Second, the above code illustrates a sensible (but unnecessary) optimization of raise statements that are statically nested in the try block. In this case, the raise operation simply jumps to the handler instead of using the global exception variable. The reason for this is that the frame pointer is already correct and need not be restored, and we know the correct value for the program counter -- it is a normal assembly-time forward reference, one we have already used when we generated the code for the to arm the handler.

Third, the special register, referred to above as SPECIALregister. This can be any register, so long as it is not touched by the code to restore the old handler. If there are multiple handlers following a try, the if statement can be replaced by a case-select construct or it can be replaced by an if-else-if cascade. The else clause catches all other exceptions, and if the else is missing, the compiler implicitly throws the exception that was not handled here.

This does suggest that Falcon is missing some features. There is no generic raise for use within an exception handler to re-throw the exception. In a handler for one of many exceptions, it would be nice to be able to re-throw whatever exception got us here the way the compiler does automatically in the case of a missing else.