UNIT IV - CODE GENERATION The final phase in compiler model is the code generator.

It takes as input an intermediate representation of the source program and produces as output an equivalent target program. The code generation techniques presented below can be used whether or not an optimizing phase occurs before code generation. Position of code generator source program intermediate code intermediate code target program

front end

code optimizer

code generator

symbol table

ISSUES IN THE DESIGN OF A CODE GENERATOR The following issues arise during the code generation phase : 1. 2. 3. 4. 5. 6. Input to code generator Target program Memory management Instruction selection Register allocation Evaluation order

1. Input to code generator: The input to the code generation consists of the intermediate representation of the source program produced by front end , together with information in the symbol table to determine run-time addresses of the data objects denoted by the names in the intermediate representation. Intermediate representation can be : a. Linear representation such as postfix notation b. Three address representation such as quadruples c. Virtual machine representation such as stack machine code d. Graphical representations such as syntax trees and dags. Prior to code generation, the front end must be scanned, parsed and translated into intermediate representation along with necessary type checking. Therefore, input to code generation is assumed to be error-free.

2. Target program: The output of the code generator is the target program. The output may be : a. Absolute machine language - It can be placed in a fixed memory location and can be executed immediately.

NOTES.PMR-INSIGNIA.ORG

b. Relocatable machine language - It allows subprograms to be compiled separately. c. Assembly language - Code generation is made easier. 3. Memory management: Names in the source program are mapped to addresses of data objects in run-time memory by the front end and code generator. It makes use of symbol table, that is, a name in a three-address statement refers to a symbol-table entry for the name. Labels in three-address statements have to be converted to addresses of instructions. For example, j : goto i generates jump instruction as follows : if i < j, a backward jump instruction with target address equal to location of code for quadruple i is generated. if i > j, the jump is forward. We must store on a list for quadruple i the location of the first machine instruction generated for quadruple j. When i is processed, the machine locations for all instructions that forward jumps to i are filled.

4. Instruction selection: The instructions of target machine should be complete and uniform. Instruction speeds and machine idioms are important factors when efficiency of target program is considered. The quality of the generated code is determined by its speed and size. The former statement can be translated into the latter statement as shown below:

5. Register allocation Instructions involving register operands are shorter and faster than those involving operands in memory. The use of registers is subdivided into two subproblems : Register allocation the set of variables that will reside in registers at a point in the program is selected.

NOTES.PMR-INSIGNIA.ORG

Register assignment the specific register that a variable will reside in is picked.

Certain machine requires even-odd register pairs for some operands and results. For example , consider the division instruction of the form : D x, y where, x dividend even register in even/odd register pair y divisor even register holds the remainder odd register holds the quotient

6. Evaluation order The order in which the computations are performed can affect the efficiency of the target code. Some computation orders require fewer registers to hold intermediate results than others. TARGET MACHINE Familiarity with the target machine and its instruction set is a prerequisite for designing a good code generator. The target computer is a byte-addressable machine with 4 bytes to a word. It has n general-purpose registers, R0, R1, . . . , Rn-1. It has two-address instructions of the form: op source, destination where, op is an op-code, and source and destination are data fields. It has the following op-codes : MOV (move source to destination) ADD (add source to destination) SUB (subtract source from destination) The source and destination of an instruction are specified by combining registers and memory locations with address modes. Address modes with their assembly-language forms
MODE FORM ADDRESS ADDED COST

absolute register indexed indirect register indirect indexed literal

M R c(R) *R *c(R) #c

M R c+contents(R) contents (R) contents(c+ contents(R)) c

1 0 1 0 1 1

NOTES.PMR-INSIGNIA.ORG

For example : MOV R0, M stores contents of Register R0 into memory location M ; MOV 4(R0), M stores the value contents(4+contents(R0)) into M.

Instruction costs : Instruction cost = 1+cost for source and destination address modes. This cost corresponds to the length of the instruction. Address modes involving registers have cost zero. Address modes involving memory location or literal have cost one. Instruction length should be minimized if space is important. Doing so also minimizes the time taken to fetch and perform the instruction. For example : MOV R0, R1 copies the contents of register R0 into R1. It has cost one, since it occupies only one word of memory. The three-address statement a : = b + c can be implemented by many different instruction sequences : i) MOV b, R0 ADD c, R0 MOV R0, a ii) MOV b, a ADD c, a cost = 6

cost = 6

iii) Assuming R0, R1 and R2 contain the addresses of a, b, and c : MOV *R1, *R0 ADD *R2, *R0 cost = 2 In order to generate good code for target machine, we must utilize its addressing capabilities efficiently.

RUN-TIME STORAGE MANAGEMENT Information needed during an execution of a procedure is kept in a block of storage called an activation record, which includes storage for names local to the procedure. The two standard storage allocation strategies are: 1. Static allocation 2. Stack allocation In static allocation, the position of an activation record in memory is fixed at compile time. In stack allocation, a new activation record is pushed onto the stack for each execution of a procedure. The record is popped when the activation ends. The following three-address statements are associated with the run-time allocation and deallocation of activation records: 1. Call, 2. Return, 3. Halt, and 4. Action, a placeholder for other statements. We assume that the run-time memory is divided into areas for: 1. Code 2. Static data 3. Stack

NOTES.PMR-INSIGNIA.ORG

Static allocation Implementation of call statement: The codes needed to implement static allocation are as follows: MOV #here + 20, callee.static_area GOTO callee.code_area /*It saves return address*/

/*It transfers control to the target code for the called procedure */

where, callee.static_area Address of the activation record callee.code_area Address of the first instruction for called procedure #here + 20 Literal return address which is the address of the instruction following GOTO. Implementation of return statement: A return from procedure callee is implemented by : GOTO *callee.static_area This transfers control to the address saved at the beginning of the activation record. Implementation of action statement: The instruction ACTION is used to implement action statement. Implementation of halt statement: The statement HALT is the final instruction that returns control to the operating system. Stack allocation Static allocation can become stack allocation by using relative addresses for storage in activation records. In stack allocation, the position of activation record is stored in register so words in activation records can be accessed as offsets from the value in this register. The codes needed to implement stack allocation are as follows: Initialization of stack: MOV #stackstart , SP Code for the first procedure HALT /* terminate execution */ /* initializes stack */

Implementation of Call statement: ADD #caller.recordsize, SP MOV #here + 16, *SP GOTO callee.code_area /* increment stack pointer */ /*Save return address */

NOTES.PMR-INSIGNIA.ORG

where, caller.recordsize size of the activation record #here + 16 address of the instruction following the GOTO Implementation of Return statement: GOTO *0 ( SP ) /*return to the caller */ /* decrement SP and restore to previous value */

SUB #caller.recordsize, SP

BASIC BLOCKS AND FLOW GRAPHS Basic Blocks A basic block is a sequence of consecutive statements in which flow of control enters at the beginning and leaves at the end without any halt or possibility of branching except at the end. The following sequence of three-address statements forms a basic block: t1 : = a * a t2 : = a * b t3 : = 2 * t2 t4 : = t1 + t3 t5 : = b * b t6 : = t4 + t5

Basic Block Construction:

Algorithm: Partition into basic blocks Input: A sequence of three-address statements Output: A list of basic blocks with each three-address statement in exactly one block Method: 1. We first determine the set of leaders, the first statements of basic blocks. The rules we use are of the following: a. The first statement is a leader. b. Any statement that is the target of a conditional or unconditional goto is a leader. c. Any statement that immediately follows a goto or conditional goto statement is a leader. 2. For each leader, its basic block consists of the leader and all statements up to but not including the next leader or the end of the program.

NOTES.PMR-INSIGNIA.ORG

Consider the following source code for dot product of two vectors a and b of length 20
begin prod :=0; i:=1; do begin prod :=prod+ a[i] * b[i]; i :=i+1; end while i <= 20 end

The three-address code for the above source program is given as :

(1) (2) end (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) end prod := 0 i := 1 while i<=20 t1 := 4* i t2 := a[t1] t3 := 4* i t4 := b[t3] t5 := t2*t4 t6 := prod+t5 prod := t6 t7 := i+1 i := t7 if i<=20 goto (3) /*compute b[i] */ /*compute a[i] */

Basic block 1: Statement (1) to (2) Basic block 2: Statement (3) to (12)

NOTES.PMR-INSIGNIA.ORG

Transformations on Basic Blocks: A number of transformations can be applied to a basic block without changing the set of expressions computed by the block. Two important classes of transformation are : Structure-preserving transformations Algebraic transformations

1. Structure preserving transformations: a) Common subexpression elimination: a:=b+c b:=ad c:=b+c d:=ad a:=b+c b:=a-d c:=b+c d:=b

Since the second and fourth expressions compute the same expression, the basic block can be transformed as above. b) Dead-code elimination: Suppose x is dead, that is, never subsequently used, at the point where the statement x : = y + z appears in a basic block. Then this statement may be safely removed without changing the value of the basic block. c) Renaming temporary variables: A statement t : = b + c ( t is a temporary ) can be changed to u : = b + c (u is a new temporary) and all uses of this instance of t can be changed to u without changing the value of the basic block. Such a block is called a normal-form block. d) Interchange of statements: Suppose a block has the following two adjacent statements: t1 : = b + c t2 : = x + y We can interchange the two statements without affecting the value of the block if and only if neither x nor y is t1 and neither b nor c is t2. 2. Algebraic transformations: Algebraic transformations can be used to change the set of expressions computed by a basic block into an algebraically equivalent set. Examples: i) x : = x + 0 or x : = x * 1 can be eliminated from a basic block without changing the set of expressions it computes. ii) The exponential statement x : = y * * 2 can be replaced by x : = y * y.

NOTES.PMR-INSIGNIA.ORG

Flow Graphs Flow graph is a directed graph containing the flow-of-control information for the set of basic blocks making up a program. The nodes of the flow graph are basic blocks. It has a distinguished initial node. E.g.: Flow graph for the vector dot product is given as follows:
prod : = 0 i:=1

B1

t1 : = 4 * i t2 : = a [ t1 ] t3 : = 4 * i t4 : = b [ t3 ] t5 : = t2 * t4 t6 : = prod + t5 prod : = t6 t7 : = i + 1 i : = t7 if i <= 20 goto B2

B2

Loops

B1 is the initial node. B2 immediately follows B1, so there is an edge from B1 to B2. The target of jump from last statement of B1 is the first statement B2, so there is an edge from B1 (last statement) to B2 (first statement). B1 is the predecessor of B2, and B2 is a successor of B1.

A loop is a collection of nodes in a flow graph such that 1. All nodes in the collection are strongly connected. 2. The collection of nodes has a unique entry. A loop that contains no other loops is called an inner loop.

NEXT-USE INFORMATION If the name in a register is no longer needed, then we remove the name from the register and the register can be used to store some other names.

NOTES.PMR-INSIGNIA.ORG

Input: Basic block B of three-address statements Output: At each statement i: x= y op z, we attach to i the liveliness and next-uses of x, y and z. Method: We start at the last statement of B and scan backwards. 1. Attach to statement i the information currently found in the symbol table regarding the next-use and liveliness of x, y and z. 2. In the symbol table, set x to not live and no next use. 3. In the symbol table, set y and z to live, and next-uses of y and z to i.

Symbol Table: Names x y z Liveliness not live Live Live Next-use no next-use i i

A SIMPLE CODE GENERATOR A code generator generates target code for a sequence of three- address statements and effectively uses registers to store operands of the statements. For example: consider the three-address statement a := b+c It can have the following sequence of codes: ADD Rj, Ri (or) ADD c, Ri (or) MOV c, Rj ADD Rj, Ri Register and Address Descriptors: A register descriptor is used to keep track of what is currently in each registers. The register descriptors show that initially all the registers are empty. An address descriptor stores the location where the current value of the name can be found at run time. Cost = 3 // move c from memory to Rj and add Cost = 2 // if c is in a memory location Cost = 1 // if Ri contains b and Rj contains c

NOTES.PMR-INSIGNIA.ORG

A code-generation algorithm: The algorithm takes as input a sequence of three-address statements constituting a basic block. For each three-address statement of the form x : = y op z , perform the following actions: 1. Invoke a function getreg to determine the location L where the result of the computation y op z should be stored. 2. Consult the address descriptor for y to determine y, the current location of y. Prefer the register for y if the value of y is currently both in memory and a register. If the value of y is not already in L, generate the instruction MOV y , L to place a copy of y in L. 3. Generate the instruction OP z , L where z is a current location of z. Prefer a register to a memory location if z is in both. Update the address descriptor of x to indicate that x is in location L. If x is in L, update its descriptor and remove x from all other descriptors. 4. If the current values of y or z have no next uses, are not live on exit from the block, and are in registers, alter the register descriptor to indicate that, after execution of x : = y op z , those registers will no longer contain y or z. Generating Code for Assignment Statements: The assignment d : = (a-b) + (a-c) + (a-c) might be translated into the following threeaddress code sequence: t:=ab u:=ac v:=t+u d:=v+u with d live at the end. Code sequence for the example is: Statements Code Generated Register descriptor Register empty t:=a-b u:=a-c MOV a, R0 SUB b, R0 MOV a , R1 SUB c , R1 ADD R1, R0 ADD R1, R0 MOV R0, d R0 contains t R0 contains t R1 contains u R0 contains v R1 contains u R0 contains d t in R0 t in R0 u in R1 u in R1 v in R0 d in R0 d in R0 and memory Address descriptor

v:=t+u

d:=v+u

NOTES.PMR-INSIGNIA.ORG

Generating Code for Indexed Assignments The table shows the code sequences generated for the indexed assignment statements a : = b [ i ] and a [ i ] : = b Statements a : = b[i] a[i] : = b Code Generated MOV b(Ri), R MOV b, a(Ri) Cost 2 3

Generating Code for Pointer Assignments The table shows the code sequences generated for the pointer assignments a : = *p and *p : = a Statements a : = *p *p : = a Code Generated MOV *Rp, a MOV a, *Rp Cost 2 2

Generating Code for Conditional Statements Statement if x < y goto z Code CMP x, y CJ< z MOV ADD MOV CJ< y, R0 z, R0 R0,x z /* jump to z if condition code is negative */

x : = y +z if x < 0 goto z

THE DAG REPRESENTATION FOR BASIC BLOCKS A DAG for a basic block is a directed acyclic graph with the following labels on nodes: 1. Leaves are labeled by unique identifiers, either variable names or constants. 2. Interior nodes are labeled by an operator symbol. 3. Nodes are also optionally given a sequence of identifiers for labels to store the computed values. DAGs are useful data structures for implementing transformations on basic blocks. It gives a picture of how the value computed by a statement is used in subsequent statements. It provides a good way of determining common sub - expressions.

NOTES.PMR-INSIGNIA.ORG

Algorithm for construction of DAG

Input: A basic block Output: A DAG for the basic block containing the following information: 1. A label for each node. For leaves, the label is an identifier. For interior nodes, an operator symbol. 2. For each node a list of attached identifiers to hold the computed values. Case (i) x : = y OP z Case (ii) x : = OP y Case (iii) x : = y Method: Step 1: If y is undefined then create node(y). If z is undefined, create node(z) for case(i). Step 2: For the case(i), create a node(OP) whose left child is node(y) and right child is node(z). ( Checking for common sub expression). Let n be this node. For case(ii), determine whether there is node(OP) with one child node(y). If not create such a node. For case(iii), node n will be node(y). Step 3: Delete x from the list of identifiers for node(x). Append x to the list of attached identifiers for the node n found in step 2 and set node(x) to n.

Example: Consider the block of three- address statements:

1. 2. 3. 4. 5. 6. 7. 8. 9. 10. t1 := 4* i t2 := a[t1] t3 := 4* i t4 := b[t3] t5 := t2*t4 t6 := prod+t5 prod := t6 t7 := i+1 i := t7 if i<=20 goto (1)

NOTES.PMR-INSIGNIA.ORG

Stages in DAG Construction

NOTES.PMR-INSIGNIA.ORG

NOTES.PMR-INSIGNIA.ORG

Application of DAGs: 1. We can automatically detect common sub expressions. 2. We can determine which identifiers have their values used in the block. 3. We can determine which statements compute values that could be used outside the block.

NOTES.PMR-INSIGNIA.ORG

GENERATING CODE FROM DAGs The advantage of generating code for a basic block from its dag representation is that, from a dag we can easily see how to rearrange the order of the final computation sequence than we can starting from a linear sequence of three-address statements or quadruples. Rearranging the order The order in which computations are done can affect the cost of resulting object code. For example, consider the following basic block: t1 : = a + b t2 : = c + d t3 : = e t2 t4 : = t1 t3 Generated code sequence for basic block: MOV a , R0 ADD b , R0 MOV c , R1 ADD d , R1 MOV R0 , t1 MOV e , R0 SUB R1 , R0 MOV t1 , R1 SUB R0 , R1 MOV R1 , t4 Rearranged basic block: Now t1 occurs immediately before t4. t2 : = c + d t3 : = e t2 t1 : = a + b t4 : = t1 t3 Revised code sequence: MOV c , R0 ADD d , R0 MOV a , R0 SUB R0 , R1 MOV a , R0 ADD b , R0 SUB R1 , R0 MOV R0 , t4 In this order, two instructions MOV R0 , t1 and MOV t1 , R1 have been saved.

NOTES.PMR-INSIGNIA.ORG

A Heuristic ordering for Dags The heuristic ordering algorithm attempts to make the evaluation of a node immediately follow the evaluation of its leftmost argument. The algorithm shown below produces the ordering in reverse. Algorithm: 1) while unlisted interior nodes remain do begin 2) select an unlisted node n, all of whose parents have been listed; 3) list n; 4) while the leftmost child m of n has no unlisted parents and is not a leaf do begin 5) list m; 6) n:=m end end Example: Consider the DAG shown below: 1 2
+ * -

+val valu 4 ues es * used used in in 5 the the 8 + bloc bloc valu +val k k es ues d e valu valu 6 + 7 c 11 12 used used +val +val +val es es in +val in ues used ues used ues the ues the a b used bloc used in used in 9 used bloc 10 +val +val in in in in the the k k ues ues Initially, the only node no unlisted parents 1 so set the n=1 at line (2) and list 1 at line (3). the with the the is bloc bloc valu valu used used bloc bloc bloc k bloc es esk Now, the left of 1, which is 2, has its parents listed, in argument in k k k so we list 2 and set n=2 at line (6). used k used the the valu valu child valu valu in leftmost in is 6, Now, at line (4) we find the of 2, which has an unlisted parent 5. Thus we bloc bloc es es es es the the select a new n at line (2), and node 3 is the only candidate. We list 3 and proceed down its left k k used used nodes so we list that. bloc bloc chain, listing 4, 5used and 6. This leaves onlyused 8 among the interior valu valu in in in in k k es list is es The resulting 1234568 and the order of evaluation is 8654321. the the the the used bloc used bloc bloc bloc in in k k k k the the bloc bloc NOTES.PMR-INSIGNIA.ORG k k

Code sequence: t8 : = d + e t6 : = a + b t5 : = t6 c t4 : = t5 * t8 t3 : = t4 e t2 : = t6 + t4 t1 : = t2 * t3 This will yield an optimal code for the DAG on machine whatever be the number of registers.

NOTES.PMR-INSIGNIA.ORG