![Page 1: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/1.jpg)
From last time: live variables
• Set D = 2 Vars
• Lattice: (D, v, ?, >, t, u) = (2Vars, µ, ; ,Vars, [, Å)
x := y op z
in
out
Fx := y op z(out) = out – { x } [ { y, z}
![Page 2: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/2.jpg)
Example: live variables
x := 5
y := x + 2
x := x + 1 y := x + 10
... y ...
![Page 3: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/3.jpg)
Revisiting assignment
x := y op z
in
out
Fx := y op z(out) = out – { x } [ { y, z}
![Page 4: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/4.jpg)
Revisiting assignment
x := y op z
in
out
Fx := y op z(out) = out – { x } [ { y, z}
![Page 5: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/5.jpg)
Theory of backward analyses
• Can formalize backward analyses in two ways
• Option 1: reverse flow graph, and then run forward problem
• Option 2: re-develop the theory, but in the backward direction
![Page 6: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/6.jpg)
Precision
• Going back to constant prop, in what cases would we lose precision?
![Page 7: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/7.jpg)
Precision
• Going back to constant prop, in what cases would we lose precision?
if (p) { x := 5;} else x := 4;}...if (p) { y := x + 1} else { y := x + 2}... y ...
if (...) { x := -1;} else x := 1;}y := x * x;... y ...
x := 5if (<expr>) { x := 6}... x ...
where <expr> is equiv to false
![Page 8: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/8.jpg)
Precision
• The first problem: Unreachable code– solution: run unreachable code removal before– the unreachable code removal analysis will do its
best, but may not remove all unreachable code
• The other two problems are path-sensitivity issues– Branch correlations: some paths are infeasible– Path merging: can lead to loss of precision
![Page 9: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/9.jpg)
MOP: meet over all paths
• Information computed at a given point is the meet of the information computed by each path to the program point
if (...) { x := -1;} else x := 1;}y := x * x;... y ...
![Page 10: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/10.jpg)
MOP
• For a path p, which is a sequence of statements [s1, ..., sn] , define: Fp(in) = Fsn
( ...Fs1(in) ... )
• In other words: Fp =
• Given an edge e, let paths-to(e) be the (possibly infinite) set of paths that lead to e
• Given an edge e, MOP(e) =
• For us, should be called JOP (ie: join, not meet)
![Page 11: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/11.jpg)
MOP vs. dataflow
• MOP is the “best” possible answer, given a fixed set of flow functions– This means that MOP v dataflow at edge in the CFG
• In general, MOP is not computable (because there can be infinitely many paths)– vs dataflow which is generally computable (if flow fns
are monotonic and height of lattice is finite)
• And we saw in our example, in general,MOP dataflow
![Page 12: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/12.jpg)
MOP vs. dataflow
• However, it would be great if by imposing some restrictions on the flow functions, we could guarantee that dataflow is the same as MOP. What would this restriction be?
x := -1;y := x * x;... y ...
x := 1;y := x * x;... y ...
Merge
x := -1; x := 1;
Merge
y := x * x;... y ...
Dataflow MOP
![Page 13: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/13.jpg)
MOP vs. dataflow
• However, it would be great if by imposing some restrictions on the flow functions, we could guarantee that dataflow is the same as MOP. What would this restriction be?
• Distributive problems. A problem is distributive if:
8 a, b . F(a t b) = F(a) t F(b)
• If flow function is distributive, then MOP = dataflow
![Page 14: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/14.jpg)
Summary of precision
• Dataflow is the basic algorithm
• To basic dataflow, we can add path-separation– Get MOP, which is same as dataflow for distributive
problems– Variety of research efforts to get closer to MOP for
non-distributive problems
• To basic dataflow, we can add path-pruning– Get branch correlation
• To basic dataflow, can add both: – meet over all feasible paths
![Page 15: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/15.jpg)
Program Representations
![Page 16: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/16.jpg)
Representing programs
• Goals
![Page 17: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/17.jpg)
Representing programs
• Primary goals– analysis is easy and effective
• just a few cases to handle• directly link related things
– transformations are easy to perform– general, across input languages and target machines
• Additional goals– compact in memory– easy to translate to and from– tracks info from source through to binary, for source-level
debugging, profilling, typed binaries– extensible (new opts, targets, language features)– displayable
![Page 18: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/18.jpg)
Option 1: high-level syntax based IR
• Represent source-level structures and expressions directly
• Example: Abstract Syntax Tree
![Page 19: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/19.jpg)
Option 2: low-level IR
• Translate input programs into low-level primitive chunks, often close to the target machine
• Examples: assembly code, virtual machine code (e.g. stack machines), three-address code, register-transfer language (RTL)
• Standard RTL instrs:
![Page 20: From last time: live variables Set D = 2 Vars Lattice: (D, v, ?, >, t, u ) = (2 Vars, µ, ;,Vars, [, Å ) x := y op z in out F x := y op z (out) = out –](https://reader035.vdocuments.mx/reader035/viewer/2022062516/56649d445503460f94a2063c/html5/thumbnails/20.jpg)
Option 2: low-level IR