diff options
| author | Cliff Click <cliffc@acm.org> | 2025-08-12 15:29:19 -0700 |
|---|---|---|
| committer | Cliff Click <cliffc@acm.org> | 2025-08-12 15:29:19 -0700 |
| commit | 6aa254dd46bede60db3350ecdb9173171f110a12 (patch) | |
| tree | ec25363593f9196da8b1c8e5f14425c2d9c10d7e | |
| parent | 1ad03924bdc78dfb6ea2fa350506580639b7f9c4 (diff) | |
| download | Simple-6aa254dd46bede60db3350ecdb9173171f110a12.tar.gz Simple-6aa254dd46bede60db3350ecdb9173171f110a12.zip | |
Update TypeAnalysis.md
| -rw-r--r-- | TypeAnalysis.md | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/TypeAnalysis.md b/TypeAnalysis.md index 25133b6d..3a857d88 100644 --- a/TypeAnalysis.md +++ b/TypeAnalysis.md @@ -53,10 +53,9 @@ points, generally to further optimize a program. At the core of the problem is a [lattice](https://en.wikipedia.org/wiki/Lattice_(order)) used to track what -values a program point can take on. Here is a common -[example](./chapter02/docs/lattice.svg) -<img src = ./chapter02/docs/lattice.svg> -for tracking integer constants. +values a program point can take on. Here is a common example for tracking integer constants: +[example](./chapter02/docs/lattice.svg) <img src = ./chapter02/docs/lattice.svg> + The lattices being used here are: * Symmetric - every lattice element has a *dual* * Complete - the *meet* of any two elements is another element |