Scalable Conditional Induction Variables (CIV) Analysis

Total Page:16

File Type:pdf, Size:1020Kb

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. Our technique re- tinct iterations do not overlap, a.k.a., output independence: quires no modifications of our dependence tests, which is k0+2*i1 = k0+2*i2 ) i1=i2. It follows that the loop in agnostic to the original shape of the subscripts, and is more Figure 1(b) can be safely parallelized. powerful than previously reported dependence tests that rely A known difficulty in performing this analysis arises on the pairwise disambiguation of read-write references. when subscripts use scalars that do not form a uniform re- We have implemented the CIV analysis in our paralleliz- currence, i.e., their stride (increment) is not constant across ing compiler and evaluated its impact on five Fortran bench- iteration space of the analyzed loop. We name such vari- marks. We have found that that there are many important ables conditional induction variables or CIV because they loops using CIV subscripts and that our analysis can lead to are typically updated (only) on some of the possible control- their scalable parallelization. This in turn has led to the par- flow paths of an iteration. For example, the loops in Fig- allelization of the benchmark programs they appear in. ures 1(a) and (c) are similar, except that in (c) both civ and the array update are performed only when condition cond(b(i)) holds. Although the recurrence computing civ 1. Introduction values can still be parallelized via a scan [2] (prefix sum) An important step in the automatic parallelization of loops is precomputation, neither CIV nor the subscript can be sum- the analysis of induction variables and their transformation marized as affine expressions of loop index i, and hence the into a form that allows their parallel evaluation. In the case of previous technique would fail. “well behaved” induction variables, that take monotonic val- This paper presents a novel induction-variable analysis ues with a constant stride, their generating sequential recur- that allows both affine and CIV based subscripts to be sum- rence can be substituted with the evaluation of closed form marized at program level, using one common representation. expression of the loop indices. This transformation enables Current solutions [3, 8, 10, 23, 26] use a two-step ap- the parallel evaluation of the induction variables. When these proach: First, CIV scalars are recognized and their proper- variables are used to form addresses of shared data struc- ties, such as monotonicity and the way they evolve inside tures, the memory references can be statically analyzed and and across iterations, are inferred. Intuitively, in our exam- possibly parallelized. Thus we can conclude that the analy- ple, this corresponds to determining that the values of civ sis of induction-variables use is crucial to loop dependence are increasing within the loop with step at most 1. This pa- analysis [1, 7, 18] and their subsequent parallelization. per does not contribute to this stage, but exploits previously For example, the loop in Figure 1(a) increments by two developed techniques [23]. Second and more relevant, each the value of k (produced by the previous iteration), and up- pair of read-write subscripts is disambiguated, by means of dates the kth element of array a. The uniform incremen- specialized dependency tests that exploit the CIV’s proper- tation of k allows to substitute this recurrence on k with ties. In our example, the cross-iteration monotonicity of the 2015 IEEE/ACM International Symposium on Code Generation and Optimization 978-1-4799-8161-8/15/$31.00 c 2015 IEEE 1-4799-8161-8/15/$31.00 ©2015 IEEE 213 CIV values dictates that the CIV value, named civ2 after our analysis simplifies CIV-summary expressions enabling being incremented in some iteration i2 is strictly greater successful verification of the relevant invariants. Second, than the value, named civ1 of any previous iteration i1. It our analysis extracts the slice of the loop that computes the follows by induction that the update of a(civ) cannot re- CIV values and evaluates it in parallel before loop execution. sult in cross-iteration (output) dependencies, i.e., the system This allows: (i) runtime verification of CIV monotonicity civ2-civ1 ≥ 1 and civ2 =civ1 has no solution. whenever this cannot be statically established, (ii) sufficient Other summarization techniques [9, 14, 16] aggregate ar- conditions for safe parallelization to be expressed in terms ray references across control-flow constructs, e.g., branches, of the CIV values at loop’s entry, end, and anywhere in be- loops, and model dependency testing as an equation on the tween, and (iii) safe parallelization in the simple case when resulted abstract sets. In practice, they were found to scale CIV are not used for indexing. The latter is not reported in better than previously developed analysis based on pairwise related work. In summary, main contributions are: accesses [9], but they do not support CIVs. • A flow-sensitive analysis that extends program level sum- This paper proposes an extension to summary-based anal- marization to support CIV-based indices and leads to the ysis that allows CIV based subscripts to use the same rep- parallelization of previously unreported loops, resentation as the affine subscripts. This enables scalable memory reference analysis without modification of the pre- • A non-trivial code generation that separates the program viously developed dependency tests. The gist of our tech- slice that performs the parallel-prefix-sum evaluation of nique is to aggregate symbolically the CIV references on ev- the CIV values from the main (parallel) computation in ery control-flow path of the analyzed loop, in terms of the which they are inserted. CIV values at the entry and end of each iteration or loop. • An evaluation of five difficult to parallelize benchmarks The analysis succeeds if (i) the symbolic-summary results with important CIV-subscripted loops, which measures are identical on all paths and (ii) they can be aggregated all runtime overheads and shows application level speed- across iterations in the interval domain. ups as high as 7:1× and on average 4:33× on 8 cores. We demonstrate the technique on the loop in Figure 1(c), Speedups of two of this paper benchmarks shown were where we use civi and civi to denote the values of civ µ b also reported in [14]. They were obtained in part by using at the entry and end of iteration i, respectively. On the the CIV technique that is presented here for the first time. THEN path, i.e., cond(b(i)) holds, the write set of array is interval W = i i , i.e., point f i g, a i [civµ+1,civb] civµ+1 2. An Intuitive Demonstration because the incremented value of civ is live at the iteration end. On the ELSE path, the write set of a is the empty set. For Figure 2(a) shows a simplified version of loop CORREC do401 uniformity of representation we express this empty set as an from BDNA benchmark, as an example of non-trivial loop interval with its lower bound greater than its upper bound. that uses both CIV and affine-based subscripts. Variable civ In particular, the interval of the THEN path matches, because uses (gated) single-static-assignment (SSA) notation [25]: i i For example, statement civ@2=γ(i.EQ.M,civ@1,civ@4) civ is not updated and so civµ+1>civb. Aggregating Wk across the first i-1 iterations results in has the semantics that variable civ@2 takes, depending on i−1 1 i the evaluation of i.EQ.M, either the value of civ@1 for the [k=1Wk = [civµ+1,civµ], where we have used civ val- k−1 k first iteration of the loop that starts at M, or the value of civ@4 ues’ monotonicity and the implicit invariant civb ≡civµ, i.e., the civ value at an iteration end is equal to the civ value for all other iterations.
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]
  • 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]
  • Formal Languages and Compilers Lecture XI—Principles of Code Optimization
    Formal Languages and Compilers Lecture XI—Principles of Code Optimization Alessandro Artale Free University of Bozen-Bolzano Faculty of Computer Science – POS Building, Room: 2.03 [email protected] http://www.inf.unibz.it/∼artale/ Formal Languages and Compilers — BSc course 2017/18 – First Semester Alessandro Artale Formal Languages and Compilers Lecture XI—Principles of Code Optimization Summary of Lecture XI Code Optimization Basic Blocks and Flow Graphs Sources of Optimization 1 Common Subexpression Elimination 2 Copy Propagation 3 Dead-Code Elimination 4 Constant Folding 5 Loop Optimization Alessandro Artale Formal Languages and Compilers Lecture XI—Principles of Code Optimization Code Optimization: Intro Intermediate Code undergoes various transformations—called Optimizations—to make the resulting code running faster and taking less space. Optimization never guarantees that the resulting code is the best possible. We will consider only Machine-Independent Optimizations—i.e., they don’t take into consideration any property of the target machine. The techniques used are a combination of Control-Flow and Data-Flow analysis. Control-Flow Analysis. Identifies loops in the flow graph of a program since such loops are usually good candidates for improvement. Data-Flow Analysis. Collects information about the way variables are used in a program. Alessandro Artale Formal Languages and Compilers Lecture XI—Principles of Code Optimization Criteria for Code-Improving Transformations The best transformations are those that yield the most benefit for the least effort. 1 A transformation must preserve the meaning of a program. It’s better to miss an opportunity to apply a transformation rather than risk changing what the program does.
    [Show full text]