Skip to content

Commit 76d7b6a

Browse files
authored
Remove duplicate MIR chapter entry (#830)
1 parent 75aa32f commit 76d7b6a

File tree

2 files changed

+6
-5
lines changed

2 files changed

+6
-5
lines changed

src/SUMMARY.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -129,9 +129,8 @@
129129
# MIR to Binaries
130130

131131
- [Prologue](./part-5-intro.md)
132-
- [The MIR (Mid-level IR)](./mir/index.md)
133-
- [MIR optimizations](./mir/optimizations.md)
134-
- [Debugging](./mir/debugging.md)
132+
- [MIR optimizations](./mir/optimizations.md)
133+
- [Debugging](./mir/debugging.md)
135134
- [Constant evaluation](./const-eval.md)
136135
- [miri const evaluator](./miri.md)
137136
- [Monomorphization](./backend/monomorph.md)

src/part-5-intro.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,14 +5,16 @@ generated any executable machine code at all! With this chapter, all of that
55
changes.
66

77
So far, we've shown how the compiler can take raw source code in text format
8-
and transform it into MIR. We have also shown how the compiler does various
8+
and transform it into [MIR]. We have also shown how the compiler does various
99
analyses on the code to detect things like type or lifetime errors. Now, we
1010
will finally take the MIR and produce some executable machine code.
1111

12+
[MIR]: ./mir/index.html
13+
1214
> NOTE: This part of a compiler is often called the _backend_ the term is a bit
1315
> overloaded because in the compiler source, it usually refers to the "codegen
1416
> backend" (i.e. LLVM or Cranelift). Usually, when you see the word "backend"
15-
> in this part, we are refering to the "codegen backend".
17+
> in this part, we are referring to the "codegen backend".
1618
1719
So what do we need to do?
1820

0 commit comments

Comments
 (0)