EECS 583 – Class 6 More Dataflow Analysis

Slides:



Advertisements
Similar presentations
SSA and CPS CS153: Compilers Greg Morrisett. Monadic Form vs CFGs Consider CFG available exp. analysis: statement gen's kill's x:=v 1 p v 2 x:=v 1 p v.
Advertisements

Data-Flow Analysis II CS 671 March 13, CS 671 – Spring Data-Flow Analysis Gather conservative, approximate information about what a program.
Course Outline Traditional Static Program Analysis –Theory Compiler Optimizations; Control Flow Graphs Data-flow Analysis – today’s class –Classic analyses.
Lecture 11: Code Optimization CS 540 George Mason University.
Chapter 9 Code optimization Section 0 overview 1.Position of code optimizer 2.Purpose of code optimizer to get better efficiency –Run faster –Take less.
1 CS 201 Compiler Construction Lecture 3 Data Flow Analysis.
Course Outline Traditional Static Program Analysis –Theory Compiler Optimizations; Control Flow Graphs Data-flow Analysis – today’s class –Classic analyses.
Data-Flow Analysis Framework Domain – What kind of solution is the analysis looking for? Ex. Variables have not yet been defined – Algorithm assigns a.
CS412/413 Introduction to Compilers Radu Rugina Lecture 37: DU Chains and SSA Form 29 Apr 02.
1 Introduction to Data Flow Analysis. 2 Data Flow Analysis Construct representations for the structure of flow-of-data of programs based on the structure.
Jeffrey D. Ullman Stanford University. 2  Generalizes: 1.Moving loop-invariant computations outside the loop. 2.Eliminating common subexpressions. 3.True.
Components of representation Control dependencies: sequencing of operations –evaluation of if & then –side-effects of statements occur in right order Data.
School of EECS, Peking University “Advanced Compiler Techniques” (Fall 2011) Dataflow Analysis Introduction Guo, Yao Part of the slides are adapted from.
Program Representations. Representing programs Goals.
School of EECS, Peking University “Advanced Compiler Techniques” (Fall 2011) Partial Redundancy Elimination Guo, Yao.
1 Data flow analysis Goal : collect information about how a procedure manipulates its data This information is used in various optimizations For example,
EECS 583 – Class 6 Dataflow Analysis University of Michigan September 26, 2011.
Common Sub-expression Elim Want to compute when an expression is available in a var Domain:
Representing programs Goals. Representing programs Primary goals –analysis is easy and effective just a few cases to handle directly link related things.
1 Data flow analysis Goal : –collect information about how a procedure manipulates its data This information is used in various optimizations –For example,
Global optimization. Data flow analysis To generate better code, need to examine definitions and uses of variables beyond basic blocks. With use- definition.
Data Flow Analysis Compiler Design Nov. 3, 2005.
Data Flow Analysis Compiler Design October 5, 2004 These slides live on the Web. I obtained them from Jeff Foster and he said that he obtained.
1 Copy Propagation What does it mean? – Given an assignment x = y, replace later uses of x with uses of y, provided there are no intervening assignments.
Direction of analysis Although constraints are not directional, flow functions are All flow functions we have seen so far are in the forward direction.
Recap from last time: live variables x := 5 y := x + 2 x := x + 1 y := x y...
Machine-Independent Optimizations Ⅰ CS308 Compiler Theory1.
Global optimization. Data flow analysis To generate better code, need to examine definitions and uses of variables beyond basic blocks. With use- definition.
Direction of analysis Although constraints are not directional, flow functions are All flow functions we have seen so far are in the forward direction.
Ben Livshits Based in part of Stanford class slides from
1 Region-Based Data Flow Analysis. 2 Loops Loops in programs deserve special treatment Because programs spend most of their time executing loops, improving.
Precision Going back to constant prop, in what cases would we lose precision?
1 CS 201 Compiler Construction Data Flow Analysis.
1 ECE 453 – CS 447 – SE 465 Software Testing & Quality Assurance Instructor Kostas Kontogiannis.
1 Data-Flow Analysis Proving Little Theorems Data-Flow Equations Major Examples.
Dataflow Analysis Topic today Data flow analysis: Section 3 of Representation and Analysis Paper (Section 3) NOTE we finished through slide 30 on Friday.
Λλ Fernando Magno Quintão Pereira P ROGRAMMING L ANGUAGES L ABORATORY Universidade Federal de Minas Gerais - Department of Computer Science P ROGRAM A.
Jeffrey D. Ullman Stanford University. 2 boolean x = true; while (x) {... // no change to x }  Doesn’t terminate.  Proof: only assignment to x is at.
Dataflow II: Finish Dataflow Analysis, Start on Classical Optimizations EECS 483 – Lecture 24 University of Michigan Wednesday, November 29, 2006.
EECS 583 – Class 6 Dataflow Analysis University of Michigan September 24, 2012.
CS 598 Scripting Languages Design and Implementation 9. Constant propagation and Type Inference.
EECS 583 – Class 5 Hyperblocks, Control Height Reduction University of Michigan September 21, 2011.
Optimization Simone Campanoni
Dataflow Analysis CS What I s Dataflow Analysis? Static analysis reasoning about flow of data in program Different kinds of data: constants, variables,
Code Optimization Overview and Examples
Data Flow Analysis Suman Jana
Control Flow IV: Control Flow Optimizations Start Dataflow Analysis
Iterative Dataflow Problems
Dataflow analysis.
Dataflow Testing G. Rothermel.
Fall Compiler Principles Lecture 8: Loop Optimizations
Topic 10: Dataflow Analysis
Factored Use-Def Chains and Static Single Assignment Forms
University Of Virginia
1. Reaching Definitions Definition d of variable v: a statement d that assigns a value to v. Use of variable v: reference to value of v in an expression.
Static Single Assignment Form (SSA)
EECS 583 – Class 8 Classic Optimization
Optimizations using SSA
Fall Compiler Principles Lecture 10: Loop Optimizations
Data Flow Analysis Compiler Design
EECS 583 – Class 7 Static Single Assignment Form
Static Single Assignment
EECS 583 – Class 8 Finish SSA, Start on Classic Optimization
EECS 583 – Class 4 If-conversion
EECS 583 – Class 4 If-conversion
EECS 583 – Class 5 Dataflow Analysis
EECS 583 – Class 7 Static Single Assignment Form
Taken largely from University of Delaware Compiler Notes
EECS 583 – Class 9 Classic and ILP Optimization
EECS 583 – Class 4 If-conversion
Presentation transcript:

EECS 583 – Class 6 More Dataflow Analysis University of Michigan September 24, 2018

Announcements & Reading Material HW 1 due tonight at midnight Hopefully you are done or very close to finishing Today’s class Compilers: Principles, Techniques, and Tools, A. Aho, R. Sethi, and J. Ullman, Addison-Wesley, 1988. (Sections: 10.5, 10.6, 10.9, 10.10 Edition 1; 9.2, 9.3 Edition 2) Material for Wednesday “Practical Improvements to the Construction and Destruction of Static Single Assignment Form,” P. Briggs, K. Cooper, T. Harvey, and L. Simpson, Software--Practice and Experience, 28(8), July 1998, pp. 859-891.

Last Time: Liveness Class Problem Answer OUT = Union(IN(succs)) IN = GEN + (OUT – KILL) IN = r3, r4 1. r1 = 3 2. r2 = r3 3. r3 = r4 GEN = r3, r4 KILL = r1, r2 Blue sets are the first iteration, Red sets are the second iteration OUT = r1, r2, r3, r4 IN = r1, r2, r3, r4  IN = r1, r2, r3, r4 (same!) 4. r1 = r1 + 1 5. r7 = r1 * r2 GEN = r1, r2 KILL = r7 OUT = r2, r3, r4, r7  OUT = r1, r2, r3, r4, r7 IN = r4, r7  IN = r1, r2, r3, r4, r7 IN = r2, r3, r7  IN = r1, r2, r3, r7 GEN = r4 KILL = NULL 6. r4 = r4 + 1 7. r4 = r3 + r2 GEN = r2, r3 KILL = r4 OUT = r7  OUT = r1, r2, r3, r4, r7 OUT = r7  OUT = r1, r2, r3, r4, r7 IN = r7  IN = r1, r2, r3, r4, r7 8. r8 = 8 GEN = NULL KILL = r8 OUT = r7, r8  OUT = r1, r2, r3, r4, r7, r8 IN = r7, r8 9. r9 = r7 + r8 GEN = r7, r8 KILL = r9 OUT = NULL

Reaching Definition Analysis (rdefs) A definition of a variable x is an operation that assigns, or may assign, a value to x A definition d reaches a point p if there is a path from the point immediately following d to p such that d is not “killed” along that path A definition of a variable is killed between 2 points when there is another definition of that variable along the path r1 = r2 + r3 kills previous definitions of r1 Liveness vs Reaching defs Liveness  variables (e.g., virtual registers), don’t care about specific users Reaching defs  operations, each def is different Forward dataflow analysis as propagation occurs from defs downwards (liveness was backward analysis)

Compute Rdef GEN/KILL Sets for each BB GEN = set of definitions created by an operation KILL = set of definitions destroyed by an operation - Assume each operation only has 1 destination for simplicity so just keep track of “ops”.. for each basic block in the procedure, X, do GEN(X) = 0 KILL(X) = 0 for each operation in sequential order in X, op, do for each destination operand of op, dest, do G = op K = {all ops which define dest – op} GEN(X) = G + (GEN(X) – K) KILL(X) = K + (KILL(X) – G) endfor

Compute Rdef IN/OUT Sets for all BBs IN = set of definitions reaching the entry of BB OUT = set of definitions leaving BB initialize IN(X) = 0 for all basic blocks X initialize OUT(X) = GEN(X) for all basic blocks X change = 1 while (change) do change = 0 for each basic block in procedure, X, do old_OUT = OUT(X) IN(X) = Union(OUT(Y)) for all predecessors Y of X OUT(X) = GEN(X) + (IN(X) – KILL(X)) if (old_OUT != OUT(X)) then endif endfor

Example Rdef Calculation IN = Union(OUT(preds)) OUT = GEN + (IN – KILL) BB1 1. r1 = MEM[r2+0] 2. r2 = MEM[r1 + 1] 3. r8 = r1 * r2 GEN = 1, 2, 3 KILL = 4, 7, 11 BB2 4. r1 = r1 + 5 5. r3 = r5 – r1 6. r7 = r3 * 2 BB3 7. r2 = 0 8. r7 = r1 + r2 9. r3 = 4 GEN = 4, 5, 6 KILL = 1, 8, 9, 10, 11, 12 GEN = 7, 8, 9 KILL = 2, 5, 6, 10, 12 BB4 10. r3 = r3 + r7 11. r1 = r2 – r8 12. r3 = r1 * 2 GEN = 11, 12 KILL = 1, 4, 5, 9, 10

Class Problem - Rdefs Compute reaching defs Calculate GEN/KILL for each BB Calculate IN/OUT for each BB 1. r1 = 3 2. r2 = r3 3. r3 = r4 4. r1 = r1 + 1 5. r7 = r1 * r2 6. r4 = r4 + 1 7. r4 = r3 + r2 8. r8 = 8 9. r9 = r7 + r8

DU/UD Chains Convenient way to access/use reaching defs info Def-Use chains Given a def, what are all the possible consumers of the operand produced Maybe consumer Use-Def chains Given a use, what are all the possible producers of the operand consumed Maybe producer

Example – DU/UD Chains 1. r1 = 3 2. r2 = r3 3. r3 = r4 4. r1 = r1 + 1

Generalizing Dataflow Analysis Transfer function How information is changed by “something” (BB) OUT = GEN + (IN – KILL) /* forward analysis */ IN = GEN + (OUT – KILL) /* backward analysis */ Meet function How information from multiple paths is combined IN = Union(OUT(predecessors)) /* forward analysis */ OUT = Union(IN(successors)) /* backward analysis */ Generalized dataflow algorithm while (change) change = false for each BB apply meet function apply transfer functions if any changes  change = true

What About All Path Problems? Up to this point Any path problems (maybe relations) Definition reaches along some path Some sequence of branches in which def reaches Lots of defs of the same variable may reach a point Use of Union operator in meet function All-path: Definition guaranteed to reach Regardless of sequence of branches taken, def reaches Can always count on this Only 1 def can be guaranteed to reach Availability (as opposed to reaching) Available definitions Available expressions (could also have reaching expressions, but not that useful)

Reaching vs Available Definitions 1:r1 = r2 + r3 2:r6 = r4 – r5 1,2 reach 1,2 available 3:r4 = 4 4:r6 = 8 1,2 reach 1,2 available 1,3,4 reach 1,3,4 available 5:r6 = r2 + r3 6:r7 = r4 – r5 1,2,3,4 reach 1 available

Available Definition Analysis (Adefs) A definition d is available at a point p if along all paths from d to p, d is not killed Remember, a definition of a variable is killed between 2 points when there is another definition of that variable along the path r1 = r2 + r3 kills previous definitions of r1 Algorithm Forward dataflow analysis as propagation occurs from defs downwards Use the Intersect function as the meet operator to guarantee the all-path requirement GEN/KILL/IN/OUT similar to reaching defs Initialization of IN/OUT is the tricky part

Compute GEN/KILL Sets for each BB (Adefs) Exactly the same as reaching defs !!! for each basic block in the procedure, X, do GEN(X) = 0 KILL(X) = 0 for each operation in sequential order in X, op, do for each destination operand of op, dest, do G = op K = {all ops which define dest – op} GEN(X) = G + (GEN(X) – K) KILL(X) = K + (KILL(X) – G) endfor

Compute IN/OUT Sets for all BBs (Adefs) U = universal set of all operations in the Procedure IN(0) = 0 OUT(0) = GEN(0) for each basic block in procedure, W, (W != 0), do IN(W) = 0 OUT(W) = U – KILL(W) change = 1 while (change) do change = 0 for each basic block in procedure, X, do old_OUT = OUT(X) IN(X) = Intersect(OUT(Y)) for all predecessors Y of X OUT(X) = GEN(X) + (IN(X) – KILL(X)) if (old_OUT != OUT(X)) then endif endfor

Available Expression Analysis (Aexprs) An expression is a RHS of an operation r2 = r3 + r4, r3+r4 is an expression An expression e is available at a point p if along all paths from e to p, e is not killed An expression is killed between 2 points when one of its source operands are redefined r1 = r2 + r3 kills all expressions involving r1 Algorithm Forward dataflow analysis as propagation occurs from defs downwards Use the Intersect function as the meet operator to guarantee the all-path requirement Looks exactly like adefs, except GEN/KILL/IN/OUT are the RHS’s of operations rather than the LHS’s

Computation of Aexpr GEN/KILL Sets We can also formulate the GEN/KILL slightly differently so you do not need to break up instructions like “r2 = r2 + 1”. for each basic block in the procedure, X, do GEN(X) = 0 KILL(X) = 0 for each operation in sequential order in X, op, do K = 0 for each destination operand of op, dest, do K += {all ops which use dest} endfor if (op not in K) G = op else G = 0 GEN(X) = G + (GEN(X) – K) KILL(X) = K + (KILL(X) – G)

Class Problem - Aexprs Calculation 1: r1 = r6 * r9 2: r2 = r2 + 1 3: r5 = r3 * r4 4: r1 = r2 + 1 5: r3 = r3 * r4 6: r8 = r3 * 2 7: r7 = r3 * r4 8: r1 = r1 + 5 9: r7 = r1 - 6 10: r8 = r2 + 1 11: r1 = r3 * r4 12: r3 = r6 * r9

Dataflow Analyses in 1 Slide Liveness Reaching Definitions/DU/UD OUT = Union(IN(succs)) IN = GEN + (OUT – KILL) IN = Union(OUT(preds)) OUT = GEN + (IN – KILL) Bottom-up dataflow Any path Keep track of variables/registers Uses of variables  GEN Defs of variables  KILL Top-down dataflow Any path Keep track of instruction IDs Defs of variables  GEN Defs of variables  KILL Available Expressions Available Definitions IN = Intersect(OUT(preds)) OUT = GEN + (IN – KILL) IN = Intersect(OUT(preds)) OUT = GEN + (IN – KILL) Top-down dataflow All path Keep track of instruction IDs Expressions of variables  GEN Defs of variables  KILL Top-down dataflow All path Keep track of instruction IDs Defs of variables  GEN Defs of variables  KILL

Some Things to Think About Liveness and rdefs are basically the same thing All dataflow is basically the same with a few parameters Meaning of gen/kill – src vs dest, variable vs operation Backward / Forward All paths / some paths (must/may) What other dataflow analysis problems can be formulated? Dataflow can be slow How to implement it efficiently? Forward analysis – DFS order Backward analysis – PostDFS order How to represent the info? Predicates Throw a monkey wrench into this stuff So, how are predicates handled?