aboutsummaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorRose Hogenson <rhogenson@posteo.net>2022-04-22 21:47:05 -0700
committerRose Hogenson <rhogenson@posteo.net>2022-04-22 21:47:05 -0700
commitf486be671e7f50e0bd219ae40e19ea6b385de116 (patch)
tree6e70c6a226da0f0f5893ae05eda3dfa37b897c73 /README.md
parentAdd a diagram of the compiler phases. (diff)
downloadchromatopelma-f486be671e7f50e0bd219ae40e19ea6b385de116.tar.zst
Fix image caption.
I think this will look the best, just repeating the same information in the alt text and in the main text. The pandoc generated version will be slightly repetitive, but it's not too bad.
Diffstat (limited to 'README.md')
-rw-r--r--README.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/README.md b/README.md
index 653c43b..cb2ba89 100644
--- a/README.md
+++ b/README.md
@@ -25,12 +25,14 @@ The cute scheme compiler (like most compilers) consists of a number of
phases that gradually transform a program from scheme code through
numerous intermediate representations. The csc compiler has 3 such
intermediate representations, not counting bytecode itself. These two
-languages are creatively called IR1, IR2, and IR3. Fig. 1 shows the
-phases of code generation.
+languages are creatively called IR1, IR2, and IR3.
![Code generation goes through several intermediate phases, named IR1,
IR2, and IR3.](design.svg)
+Fig. 1 shows the phases of code generation. Code generation goes through
+several intermediate phases, named IR1, IR2, and IR3.
+
### IR1
IR1 can be thought of as scheme code with all the macros expanded. An