Automatic Methods for Program Transformation

Total Page:16

File Type:pdf, Size:1020Kb

Automatic Methods for Program Transformation University of London Imperial College of Science, Technology and Medicine Department of Computing Automatic Methods for Program Transformation by CHIN Wei Ngan This thesis is submitted in part fulfilment of the requirements for the degree of Doctor of Philosophy (PhD) and the Diploma of the Imperial College (DIC) Submitted - March 1990 Examined - May 1990 Abstract The transformational approach to software development is recognised as an important formal route for software construction. One major benefit of this approach is the possibility of providing machine assistance to this development process. This thesis works towards this goal by systematizing four major classes of transformations into automated methods (or tactics). The first class of transformations involves the fusion of composed expressions to eliminate unnecessary intermediate data structures and function calls. A producer-consumer model of functions is introduced to explain this transformation. With this model, we show how the deforestation algorithm of Wadler can be extended to all first-order programs. The extended transformation algorithm is presented, termination proof given and further improvements suggested. A similar consideration is also developed for compositions in set abstractions. The second class of transformations involves the removal of certain higher-order features from well-typed programs. Three transformation algorithms are developed. Two of them are directly concerned with the removal of higher-order features. Termination proofs for these algorithms are given. A third algorithm preserves full laziness in a manner compatible with higher-order features removal. With these transformations, the extension of deforestation to higher-order programs is also developed. The third class of transformations concerns the removal of redundant computation through tup ling. A survey of past techniques is presented, followed by the development of a new analysis technique to discover eureka tuples to remove redundancy. This new technique makes novel use of selection orderings to search for eureka tuples. We give some methods to determine appropriate orderings and provide extensions to the basic analysis technique. The last class of transformations involves the use of constraints (or invariants) to help improve recursive programs. Both the finite differencing tactic and a new base-case filter promotion tactic are part of this category of transformations. The necessary laws and semantic conditions for these two tactics are systematized. Acknowledgements The author would like to acknowledge the support received from the following parties: National University of Singapore for generously providing the financial support and study leave necessary to pursue this work. John Darlington for the supervision, insight and guidance necessary to bring my research to fruition. Phil Wadler for inspiring much of the work done in Chapter 3 and 4. Chris Hankin for clarifying my thoughts on abstract interpretation David Lillie, Guido Jouret and David Sharp for acting as sounding boards and verifiers for some of my late ideas. D Lillie and G Jouret also provided invaluable feedback on the thesis. Peter Harrison, Tony Field, David Sands, Hessam and Paul Kelly for carefully reading and commenting on various parts of this thesis Helen, Keith, Nigel and Lyndon for bailing me out of the technical intrigues of programming H o p e + and the transformation-based environment The Rest of Functional Programming Section for contributing to a most stimulating place for research. Bee Hoon for her understanding and encouragement. Dedications To Mum and Dad Table of Contents 1. Introduction 1 1.1. The Software Problem 1 1.2. A Suitable Language for Specification and Transformation 2 1.2.1. An Extended Functional Language 3 1.2.2. Types of Abstractions Available 4 1.2.2.1. Data Abstraction 4 1.2.2.2. Program Abstraction 5 1.2.2.3. Specification Abstraction 5 1.2.2.4. System Abstraction 7 1.3. A Suitable Program Transformation Methodology 7 1.3.1. Catalogue versus Generative Set Systems 8 1.3.2. Desirable Criteria for Transformation Systems 9 1.3.3. The Unfold/Fold Methodology 10 1.3.4. Correctness 12 1.3.5. Completeness 13 1.4. Contribution of Thesis 14 2. Automatic Methods 18 2.1. A Pitfall to Avoid 18 2.2. A Comprehensive Transformation System 19 2.2.1. Transformation Processor and the Script Language 20 2.2.2. Program Repository 22 2.2.3. LemmaLibraiy 22 2.2.4. Inference Sub-System 23 2.2.5. Methods or Tactics Bank. 24 2.3. Common Structure of Tactics 25 2.4. An Algorithmic Tactic: Removing Useless Parameters 26 2.4.1. A Simple Functional Language 26 2.4.2. Phase 1: Analysis for Useless Parameters 27 2.4.3. Phase 2: Transformation 30 2.4.3.1. Transformation Algorithm 30 2.4.3.2. An Example 32 2.4.3.3. A Version of t/ which Carries the Definition Set 33 2.4.3.4. A Version of V which Returns Scripts 34 2.5. A Schematic Tactic: Conversion-to-Iteration 35 2.5.1. Constructing a Schematic Rule 36 2.5.2. Applying the Schematic Rule 3 8 2.5.3. The Stages for Rule Applications 41 2.5.4. Wider Applicability of our Approach 42 2.5.5. Benefits of Schematic Rules 43 2.6. Summary of Chapter 2 44 3. Fusion 45 3.1. Introduction 45 3.1.1. Two Forms of Composition 45 3.1.1.1. Functional Composition 45 3.1.1.2. Set Abstraction 47 3.1.2. Consumer-Producer Model 49 (i) 3.2. W adler’s Deforestation 50 3.2.1. Pure Treeless Form 51 3.2.2. Deforestation Theorem 5 2 3.2.3. T ransformation Algorithm 5 3 3.2.4. Making all Steps Explicit 54 3.2.5. Proof for Deforestation Theorem 55 3.2.6. Blazed Treeless Form 59 3.3. Our Extension to Deforestation 61 3.3.1. Parameter-Based Annotation Scheme 62 3.3.1.1. V ariable-Only Criterion 62 3.3.1.2. Linearity Criterion 63 3.3.1.3. Annotation Scheme 64 3.3.2. Extended Treeless Form 65 3.3.3. Extended Deforestation Theorem 66 3.3.4. Transformation Algorithm 67 3.3.5. An Example 71 3.3.6. Proof for Extended Deforestation Theorem 7 2 3.3.7. A Minor Improvement to Extended Deforestation 82 3.4. Deforestation for First-Order Expressions 83 3.4.1. Universal Treelessness 84 3.4.2. Proof of Universal Deforestation Theorem 86 3.4.3. Converting Functions to Universal Treeless Form 87 3.4.3.1. Bottom-Up Conversion Strategy 88 3.4.3.2. Conversion for Non-Recursive Functions 8 8 3.4.3.3. Conversion for Recursive Functions 89 3.4.4. Example of Universal Treeless Conversion 90 3.5. Further Improvements to Deforestation 92 3.5.1. Eliminating Unnecessary Mutual Recursive Functions 93 3.5.2. Linearising Pattern-Matching Parameters 94 3.5.3. Laws to Improve Deforestation 95 3.6. Supercompilation - A Related Work < 96 3.7. Fusion in Set Abstractions 97 3.7.1. Filter Promotion 9 8 3.7.1.1. Desirable Filter Form 98 3.7.1.2. Desirable Generator Form 99 3.7.1.3. Transformation Algorithm 100 3.7.1.4. An Example 102 3.7.1.5. Undesirable Expression Forms 104 3.7.1.5.1. Undesirable Generators 104 3.7.1.5.2. Undesirable Filters 105 3.7.1.6. An Extension (Patterns instead of Variables) 107 3.7.2. Fusions between Generators and Processors 109 3.7.2.1. Desirable Processor Form 109 3.7.2.2. Transformation Algorithm 110 3.7.2.3. An Example 111 3.8. Summary of Chapter 3 112 4. Higher-Order Removal 114 4.1. Introduction 114 4.1.1. A Simple Higher Order Language 115 4.1.2. Overview of General Application Elimination 116 4.1.3. Overview of Higher-Order Argument Elimination 117 4.1.4. Overview of Full Laziness Technique 119 4.1.5. Overview of Fully Lazy Higher-Order Argument Elimination 121 4.1.6. Outline of Stages for the Higher-Order Removal Tactic 122 (ii) 4.2. Elimination of General Applications 124 4.2.1. Transformation Algorithm, A 124 4.2.2. An Example 127 4.2.3. Proof of Theorem 4.2 128 4.2.3.1. Proof for Lemma 4.3 (on applyless form) 128 4.2.3.2. Proof for Lemma 4.4 (on efficiency) 128 4.2.3.3. Proof for Lemma 4.5 (on termination) 128 4.3. Elimination of Higher-Order Arguments 130 4.3.1. Higher-Order Specialised Form 131 4.3.2. Transformation Algorithm, 131 4.3.3. A Simple Example 135 4.3.4. An Optimisation for the Nested Rules 135 4.3.5. Further Examples 136 4.3.5.1. mapreduce 136 4.3.5.2. twice_map 137 4.3.5.3. fix-point operator and % 12 137 4.3.6. Proof of Theorem 4.7 139 4.4. Full Laziness Concern 145 4.4.1. Various Techniques for Full Laziness 146 4.4.1.1. L(a) Extract out GT-MFEs from lambda abstractions. 146 4.4.1.2. L(b) Convert grounded GT-MFEs to CFs 146 4.4.1.3. £(c) Direct Unfolds for non-recursive function calls 147 4.4.1.4. L(d) Indirect Unfolds by Re-Defining non-recursive functions. 147 4.4.1.5. Recursive Functions and the Space Leak Problem. 148 4.4.2. Full Laziness Transformation Algorithm 149 4.4.2.1. The L rules 149 4.4.2.2. The Ernies 151 4.4.2.3. The rules 153 4.4.3. Fully Lazy Elimination of Higher-Order Arguments 155 4.4.4. An Example.-. - • 156 4.4.5. Possible Losses of Efficiency 157 4.4.5.1.
Recommended publications
  • Equality Saturation: a New Approach to Optimization
    Logical Methods in Computer Science Vol. 7 (1:10) 2011, pp. 1–37 Submitted Oct. 12, 2009 www.lmcs-online.org Published Mar. 28, 2011 EQUALITY SATURATION: A NEW APPROACH TO OPTIMIZATION ROSS TATE, MICHAEL STEPP, ZACHARY TATLOCK, AND SORIN LERNER Department of Computer Science and Engineering, University of California, San Diego e-mail address: {rtate,mstepp,ztatlock,lerner}@cs.ucsd.edu Abstract. Optimizations in a traditional compiler are applied sequentially, with each optimization destructively modifying the program to produce a transformed program that is then passed to the next optimization. We present a new approach for structuring the optimization phase of a compiler. In our approach, optimizations take the form of equality analyses that add equality information to a common intermediate representation. The op- timizer works by repeatedly applying these analyses to infer equivalences between program fragments, thus saturating the intermediate representation with equalities. Once saturated, the intermediate representation encodes multiple optimized versions of the input program. At this point, a profitability heuristic picks the final optimized program from the various programs represented in the saturated representation. Our proposed way of structuring optimizers has a variety of benefits over previous approaches: our approach obviates the need to worry about optimization ordering, enables the use of a global optimization heuris- tic that selects among fully optimized programs, and can be used to perform translation validation, even on compilers other than our own. We present our approach, formalize it, and describe our choice of intermediate representation. We also present experimental results showing that our approach is practical in terms of time and space overhead, is effective at discovering intricate optimization opportunities, and is effective at performing translation validation for a realistic optimizer.
    [Show full text]
  • Scalable Conditional Induction Variables (CIV) Analysis
    Scalable Conditional Induction Variables (CIV) Analysis ifact Cosmin E. Oancea Lawrence Rauchwerger rt * * Comple A t te n * A te s W i E * s e n l C l o D C O Department of Computer Science Department of Computer Science and Engineering o * * c u e G m s E u e C e n R t v e o d t * y * s E University of Copenhagen Texas A & M University a a l d u e a [email protected] [email protected] t Abstract k = k0 Ind. k = k0 DO i = 1, N DO i =1,N Var. DO i = 1, N IF(cond(b(i)))THEN Subscripts using induction variables that cannot be ex- k = k+2 ) a(k0+2*i)=.. civ = civ+1 )? pressed as a formula in terms of the enclosing-loop indices a(k)=.. Sub. ENDDO a(civ) = ... appear in the low-level implementation of common pro- ENDDO k=k0+MAX(2N,0) ENDIF ENDDO gramming abstractions such as filter, or stack operations and (a) (b) (c) pose significant challenges to automatic parallelization. Be- Figure 1. Loops with affine and CIV array accesses. cause the complexity of such induction variables is often due to their conditional evaluation across the iteration space of its closed-form equivalent k0+2*i, which enables its in- loops we name them Conditional Induction Variables (CIV). dependent evaluation by all iterations. More importantly, This paper presents a flow-sensitive technique that sum- the resulted code, shown in Figure 1(b), allows the com- marizes both such CIV-based and affine subscripts to pro- piler to verify that the set of points written by any dis- gram level, using the same representation.
    [Show full text]
  • Induction Variable Analysis with Delayed Abstractions1
    Induction Variable Analysis with Delayed Abstractions1 SEBASTIAN POP, and GEORGES-ANDRE´ SILBER CRI, Mines Paris, France and ALBERT COHEN ALCHEMY group, INRIA Futurs, Orsay, France We present the design of an induction variable analyzer suitable for the analysis of typed, low-level, three address representations in SSA form. At the heart of our analyzer stands a new algorithm that recognizes scalar evolutions. We define a representation called trees of recurrences that is able to capture different levels of abstractions: from the finer level that is a subset of the SSA representation restricted to arithmetic operations on scalar variables, to the coarser levels such as the evolution envelopes that abstract sets of possible evolutions in loops. Unlike previous work, our algorithm tracks induction variables without prior classification of a few evolution patterns: different levels of abstraction can be obtained on demand. The low complexity of the algorithm fits the constraints of a production compiler as illustrated by the evaluation of our implementation on standard benchmark programs. Categories and Subject Descriptors: D.3.4 [Programming Languages]: Processors—compilers, interpreters, optimization, retargetable compilers; F.3.2 [Logics and Meanings of Programs]: Semantics of Programming Languages—partial evaluation, program analysis General Terms: Compilers Additional Key Words and Phrases: Scalar evolutions, static analysis, static single assignment representation, assessing compilers heuristics regressions. 1Extension of Conference Paper:
    [Show full text]
  • Strength Reduction of Induction Variables and Pointer Analysis – Induction Variable Elimination
    Loop optimizations • Optimize loops – Loop invariant code motion [last time] Loop Optimizations – Strength reduction of induction variables and Pointer Analysis – Induction variable elimination CS 412/413 Spring 2008 Introduction to Compilers 1 CS 412/413 Spring 2008 Introduction to Compilers 2 Strength Reduction Induction Variables • Basic idea: replace expensive operations (multiplications) with • An induction variable is a variable in a loop, cheaper ones (additions) in definitions of induction variables whose value is a function of the loop iteration s = 3*i+1; number v = f(i) while (i<10) { while (i<10) { j = 3*i+1; //<i,3,1> j = s; • In compilers, this a linear function: a[j] = a[j] –2; a[j] = a[j] –2; i = i+2; i = i+2; f(i) = c*i + d } s= s+6; } •Observation:linear combinations of linear • Benefit: cheaper to compute s = s+6 than j = 3*i functions are linear functions – s = s+6 requires an addition – Consequence: linear combinations of induction – j = 3*i requires a multiplication variables are induction variables CS 412/413 Spring 2008 Introduction to Compilers 3 CS 412/413 Spring 2008 Introduction to Compilers 4 1 Families of Induction Variables Representation • Basic induction variable: a variable whose only definition in the • Representation of induction variables in family i by triples: loop body is of the form – Denote basic induction variable i by <i, 1, 0> i = i + c – Denote induction variable k=i*a+b by triple <i, a, b> where c is a loop-invariant value • Derived induction variables: Each basic induction variable i defines
    [Show full text]
  • Generalizing Loop-Invariant Code Motion in a Real-World Compiler
    Imperial College London Department of Computing Generalizing loop-invariant code motion in a real-world compiler Author: Supervisor: Paul Colea Fabio Luporini Co-supervisor: Prof. Paul H. J. Kelly MEng Computing Individual Project June 2015 Abstract Motivated by the perpetual goal of automatically generating efficient code from high-level programming abstractions, compiler optimization has developed into an area of intense research. Apart from general-purpose transformations which are applicable to all or most programs, many highly domain-specific optimizations have also been developed. In this project, we extend such a domain-specific compiler optimization, initially described and implemented in the context of finite element analysis, to one that is suitable for arbitrary applications. Our optimization is a generalization of loop-invariant code motion, a technique which moves invariant statements out of program loops. The novelty of the transformation is due to its ability to avoid more redundant recomputation than normal code motion, at the cost of additional storage space. This project provides a theoretical description of the above technique which is fit for general programs, together with an implementation in LLVM, one of the most successful open-source compiler frameworks. We introduce a simple heuristic-driven profitability model which manages to successfully safeguard against potential performance regressions, at the cost of missing some speedup opportunities. We evaluate the functional correctness of our implementation using the comprehensive LLVM test suite, passing all of its 497 whole program tests. The results of our performance evaluation using the same set of tests reveal that generalized code motion is applicable to many programs, but that consistent performance gains depend on an accurate cost model.
    [Show full text]
  • Efficient Symbolic Analysis for Optimizing Compilers*
    Efficient Symbolic Analysis for Optimizing Compilers? Robert A. van Engelen Dept. of Computer Science, Florida State University, Tallahassee, FL 32306-4530 [email protected] Abstract. Because most of the execution time of a program is typically spend in loops, loop optimization is the main target of optimizing and re- structuring compilers. An accurate determination of induction variables and dependencies in loops is of paramount importance to many loop opti- mization and parallelization techniques, such as generalized loop strength reduction, loop parallelization by induction variable substitution, and loop-invariant expression elimination. In this paper we present a new method for induction variable recognition. Existing methods are either ad-hoc and not powerful enough to recognize some types of induction variables, or existing methods are powerful but not safe. The most pow- erful method known is the symbolic differencing method as demonstrated by the Parafrase-2 compiler on parallelizing the Perfect Benchmarks(R). However, symbolic differencing is inherently unsafe and a compiler that uses this method may produce incorrectly transformed programs without issuing a warning. In contrast, our method is safe, simpler to implement in a compiler, better adaptable for controlling loop transformations, and recognizes a larger class of induction variables. 1 Introduction It is well known that the optimization and parallelization of scientific applica- tions by restructuring compilers requires extensive analysis of induction vari- ables and dependencies
    [Show full text]
  • Compiler-Based Code-Improvement Techniques
    Compiler-Based Code-Improvement Techniques KEITH D. COOPER, KATHRYN S. MCKINLEY, and LINDA TORCZON Since the earliest days of compilation, code quality has been recognized as an important problem [18]. A rich literature has developed around the issue of improving code quality. This paper surveys one part of that literature: code transformations intended to improve the running time of programs on uniprocessor machines. This paper emphasizes transformations intended to improve code quality rather than analysis methods. We describe analytical techniques and specific data-flow problems to the extent that they are necessary to understand the transformations. Other papers provide excellent summaries of the various sub-fields of program analysis. The paper is structured around a simple taxonomy that classifies transformations based on how they change the code. The taxonomy is populated with example transformations drawn from the literature. Each transformation is described at a depth that facilitates broad understanding; detailed references are provided for deeper study of individual transformations. The taxonomy provides the reader with a framework for thinking about code-improving transformations. It also serves as an organizing principle for the paper. Copyright 1998, all rights reserved. You may copy this article for your personal use in Comp 512. Further reproduction or distribution requires written permission from the authors. 1INTRODUCTION This paper presents an overview of compiler-based methods for improving the run-time behavior of programs — often mislabeled code optimization. These techniques have a long history in the literature. For example, Backus makes it quite clear that code quality was a major concern to the implementors of the first Fortran compilers [18].
    [Show full text]
  • Lecture 1 Introduction
    Lecture 1 Introduction • What would you get out of this course? • Structure of a Compiler • Optimization Example Carnegie Mellon Todd C. Mowry 15-745: Introduction 1 What Do Compilers Do? 1. Translate one language into another – e.g., convert C++ into x86 object code – difficult for “natural” languages, but feasible for computer languages 2. Improve (i.e. “optimize”) the code – e.g, make the code run 3 times faster – driving force behind modern processor design Carnegie Mellon 15-745: Introduction 2 Todd C. Mowry What Do We Mean By “Optimization”? • Informal Definition: – transform a computation to an equivalent but “better” form • in what way is it equivalent? • in what way is it better? • “Optimize” is a bit of a misnomer – the result is not actually optimal Carnegie Mellon 15-745: Introduction 3 Todd C. Mowry How Can the Compiler Improve Performance? Execution time = Operation count * Machine cycles per operation • Minimize the number of operations – arithmetic operations, memory acesses • Replace expensive operations with simpler ones – e.g., replace 4-cycle multiplication with 1-cycle shift • Minimize cache misses Processor – both data and instruction accesses • Perform work in parallel cache – instruction scheduling within a thread memory – parallel execution across multiple threads • Related issue: minimize object code size – more important on embedded systems Carnegie Mellon 15-745: Introduction 4 Todd C. Mowry Other Optimization Goals Besides Performance • Minimizing power and energy consumption • Finding (and minimizing the
    [Show full text]
  • Simplification of Array Access Patterns for Compiler Optimizations *
    Simplification of Array Access Patterns for Compiler Optimizations * Yunheung Paek$ Jay Hoeflingert David Paduat $ New Jersey Institute of Technology paekQcis.njit.edu t University of Illinois at Urbana-Champaign {hoef ling ,padua}Buiuc . edu Abstract Existing array region representation techniques are sen- sitive to the complexity of array subscripts. In general, these techniques are very accurate and efficient for sim- ple subscript expressions, but lose accuracy or require potentially expensive algorithms for complex subscripts. We found that in scientific applications, many access patterns are simple even when the subscript expressions Figure 1: Access to array X with indices ik, 1 5 k < d, in are complex. In this work, we present a new, general the program ScCtiOn ‘P such that 15 5 ik 5 Uk. array access representation and define operations for it. This allows us to aggregate and simplify the rep- resentation enough that precise region operations may be determined. For this purpose, when doing array ac- be applied to enable compiler optimizations. Our ex- cess analysis for the references to an array, a compiler periments show that these techniques hold promise for would first calculate a Reference Descriptor (RD) for speeding up applications. each, which extends the array reference with range con- straints. For instance, given that il: ranges from lk to 1 Introduction uk in p (for k = 1,2, * - -, d), the RD for the access in Figure 1 is The array is one of the most important data structures “X(81(i), .92(i), e-s, am(i)) subject to in imperative programs. Particularly in numerical ap- lk < ik 5 Uk, for k = 1,2, * * ‘, d.” plications, almost all computation is performed on ar- rays.
    [Show full text]
  • Dependence Testing Without Induction Variable Substitution Albert Cohen, Peng Wu
    Dependence Testing Without Induction Variable Substitution Albert Cohen, Peng Wu To cite this version: Albert Cohen, Peng Wu. Dependence Testing Without Induction Variable Substitution. Workshop on Compilers for Parallel Computers (CPC), 2001, Edimburgh, United Kingdom. hal-01257313 HAL Id: hal-01257313 https://hal.archives-ouvertes.fr/hal-01257313 Submitted on 17 Jan 2016 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Dependence Testing Without Induction Variable Substitution z Albert Cohen y Peng Wu y A3 Project, INRIA Rocquencourt z Department of Computer Science, University of Illinois 78153 Le Chesnay, France Urbana, IL 61801, USA [email protected] [email protected] Abstract We present a new approach to dependence testing in the presence of induction variables. Instead of looking for closed form expressions, our method computes monotonic evolution which captures the direction in which the value of a variable changes. This information is used for dependence testing of array references. Under this scheme, closed form computation and induction variable substitution can be delayed until after the dependence test and be performed on-demand. The technique can be extended to dynamic data structures, using either pointer-based implementations or standard object-oriented containers.
    [Show full text]
  • Redundant Computation Elimination Optimizations
    Redundant Computation Elimination Optimizations CS2210 Lecture 20 CS2210 Compiler Design 2004/5 Redundancy Elimination ■ Several categories: ■ Value Numbering ■ local & global ■ Common subexpression elimination (CSE) ■ local & global ■ Loop-invariant code motion ■ Partial redundancy elimination ■ Most complex ■ Subsumes CSE & loop-invariant code motion CS2210 Compiler Design 2004/5 Value Numbering ■ Goal: identify expressions that have same value ■ Approach: hash expression to a hash code ■ Then have to compare only expressions that hash to same value CS2210 Compiler Design 2004/5 1 Example a := x | y b := x | y t1:= !z if t1 goto L1 x := !z c := x & y t2 := x & y if t2 trap 30 CS2210 Compiler Design 2004/5 Global Value Numbering ■ Generalization of value numbering for procedures ■ Requires code to be in SSA form ■ Crucial notion: congruence ■ Two variables are congruent if their defining computations have identical operators and congruent operands ■ Only precise in SSA form, otherwise the definition may not dominate the use CS2210 Compiler Design 2004/5 Value Graphs ■ Labeled, directed graph ■ Nodes are labeled with ■ Operators ■ Function symbols ■ Constants ■ Edges point from operator (or function) to its operands ■ Number labels indicate operand position CS2210 Compiler Design 2004/5 2 Example entry receive n1(val) i := 1 1 B1 j1 := 1 i3 := φ2(i1,i2) B2 j3 := φ2(j1,j2) i3 mod 2 = 0 i := i +1 i := i +3 B3 4 3 5 3 B4 j4:= j3+1 j5:= j3+3 i2 := φ5(i4,i5) j3 := φ5(j4,j5) B5 j2 > n1 exit CS2210 Compiler Design 2004/5 Congruence Definition ■ Maximal relation on the value graph ■ Two nodes are congruent iff ■ They are the same node, or ■ Their labels are constants and the constants are the same, or ■ They have the same operators and their operands are congruent ■ Variable equivalence := x and y are equivalent at program point p iff they are congruent and their defining assignments dominate p CS2210 Compiler Design 2004/5 Global Value Numbering Algo.
    [Show full text]
  • CSC D70: Compiler Optimization
    CSC D70: Compiler Optimization Prof. Gennady Pekhimenko University of Toronto Winter 2018 The content of this lecture is adapted from the lectures of Todd Mowry and Phillip Gibbons CSC D70: Compiler Optimization Introduction, Logistics Prof. Gennady Pekhimenko University of Toronto Winter 2018 The content of this lecture is adapted from the lectures of Todd Mowry and Phillip Gibbons Summary • Syllabus – Course Introduction, Logistics, Grading • Information Sheet – Getting to know each other • Assignments • Learning LLVM • Compiler Basics 3 Syllabus: Who Are We? 4 Gennady (Gena) Pekhimenko Assistant Professor, Instructor [email protected] http://www.cs.toronto.edu/~pekhimenko/ Office: BA 5232 / IC 454 PhD from Carnegie Mellon Worked at Microsoft Research, NVIDIA, IBM Research interests: computer architecture, systems, machine learning, compilers, hardware acceleration, bioinformatics Computer Systems and Networking Group (CSNG) EcoSystem Group Bojian Zheng MSc. Student, TA [email protected] Office: BA 5214 D02 BSc. from UofT ECE Research interests: computer architecture, GPUs, machine learning Computer Systems and Networking Group (CSNG) EcoSystem Group Course Information: Where to Get? • Course Website: http://www.cs.toronto.edu/~pekhimenko/courses/cscd70- w18/ – Announcements, Syllabus, Course Info, Lecture Notes, Tutorial Notes, Assignments • Piazza: https://piazza.com/utoronto.ca/winter2018/cscd70/home – Questions/Discussions, Syllabus, Announcements • Blackboard – Emails/announcements • Your email 7 Useful Textbook 8 CSC D70: Compiler Optimization Compiler Introduction Prof. Gennady Pekhimenko University of Toronto Winter 2018 The content of this lecture is adapted from the lectures of Todd Mowry and Phillip Gibbons Introduction to Compilers • What would you get out of this course? • Structure of a Compiler • Optimization Example 10 What Do Compilers Do? 1.
    [Show full text]