summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCliff Click <cliffc@acm.org>2025-08-12 15:28:25 -0700
committerCliff Click <cliffc@acm.org>2025-08-12 15:28:25 -0700
commit1ad03924bdc78dfb6ea2fa350506580639b7f9c4 (patch)
treeaf54a729fd77b561d55ec22172a2e213486a2e8c
parenta3ce40b7ba8d80326a3d2d16eea738e62d28ff6f (diff)
downloadSimple-1ad03924bdc78dfb6ea2fa350506580639b7f9c4.tar.gz
Simple-1ad03924bdc78dfb6ea2fa350506580639b7f9c4.zip
Update TypeAnalysis.md
-rw-r--r--TypeAnalysis.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/TypeAnalysis.md b/TypeAnalysis.md
index 0924c06f..25133b6d 100644
--- a/TypeAnalysis.md
+++ b/TypeAnalysis.md
@@ -54,7 +54,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) for tracking integer constants.
+[example](./chapter02/docs/lattice.svg)
+<img src = ./chapter02/docs/lattice.svg>
+for tracking integer constants.
The lattices being used here are:
* Symmetric - every lattice element has a *dual*
* Complete - the *meet* of any two elements is another element