├── .gitignore
├── 2019-Fall
    ├── L17-IR.md
    ├── L18-IR.md
    ├── L19SDT-1.md
    ├── L20SDT-2.md
    ├── L21SDT-3.md
    ├── bace-lecture-01.mkv
    ├── bace-lecture-01.pdf
    ├── bace-lecture-02.pdf
    ├── bace-lecture-03.pdf
    ├── bace-lecture-04.pdf
    ├── bace-lecture-05.pdf
    ├── bace-lecture-06.pdf
    ├── bace-lecture-09.pdf
    ├── bace-lecture-10.pdf
    ├── bace-lecture-11.pdf
    └── bace-lecture-12.pdf
├── 2021-Spring
    ├── S03E01-Intro.pdf
    └── local stack slot allocation.pdf
├── LICENSE
├── README.md
└── doc
    ├── Makefile
    ├── bace lecture.rst
    ├── conf.py
    ├── images
        ├── image01.png
        ├── image02.png
        ├── image03.png
        ├── image04.png
        ├── image05.png
        ├── image06.png
        ├── image07.png
        ├── image08.png
        ├── image09.png
        ├── image10.png
        ├── image11.png
        ├── image12.png
        ├── image13.png
        ├── image14.png
        ├── image15.png
        ├── image16.png
        ├── image17.png
        ├── image18.png
        ├── image19.png
        ├── image20.png
        ├── image21.png
        ├── image22.png
        ├── image23.png
        ├── image24.png
        ├── image25.png
        ├── image26.png
        ├── image27.png
        ├── image28.png
        ├── image29.png
        ├── image30.png
        └── image31.png
    ├── index.rst
    └── make.bat


/.gitignore:
--------------------------------------------------------------------------------
 1 | # Prerequisites
 2 | *.d
 3 | 
 4 | # Compiled Object files
 5 | *.slo
 6 | *.lo
 7 | *.o
 8 | *.obj
 9 | 
10 | # Precompiled Headers
11 | *.gch
12 | *.pch
13 | 
14 | # Compiled Dynamic libraries
15 | *.so
16 | *.dylib
17 | *.dll
18 | 
19 | # Fortran module files
20 | *.mod
21 | *.smod
22 | 
23 | # Compiled Static libraries
24 | *.lai
25 | *.la
26 | *.a
27 | *.lib
28 | 
29 | # Executables
30 | *.exe
31 | *.out
32 | *.app
33 | .DS_Store
34 | 


--------------------------------------------------------------------------------
/2019-Fall/L17-IR.md:
--------------------------------------------------------------------------------
  1 | # 编译技术入门与实战
  2 | 
  3 | ## Cooper 教授 L17-IR 评注
  4 | 
  5 | ### 0
  6 | 
  7 | 从业多年之后才能看懂里面的感悟
  8 | 
  9 | ### 1
 10 | 
 11 | Mea culpa is a Latin phrase that means "through my fault" and is an acknowledgement of having done wrong. Grammatically, meā culpā is in the ablative case, with an instrumental meaning. Wikipedia
 12 | 
 13 | amnesty 大赦天下
 14 | 
 15 | ### 2
 16 | 
 17 | 这里都是一些经验之谈。
 18 | 刚开始肯定无法体会，没关系的。
 19 | 
 20 | cusp
 21 | /kəsp/
 22 | Learn to pronounce
 23 | noun
 24 | noun: cusp; plural noun: cusps
 25 | 
 26 |     1.
 27 |     a point of transition between two different states.
 28 |     "those on the cusp of adulthood"
 29 |     2.
 30 |     a pointed end where two curves meet.
 31 | 
 32 | Oxford Dict
 33 | 
 34 | 这种乐趣门外汉是感受不到的，正所谓「初闻不识曲中意，再闻已是曲中人」。
 35 | 
 36 | 
 37 | ### 3
 38 | 
 39 | 说了编译器领域的共识。
 40 | 
 41 | 前端 --IR--> 优化器
 42 | 
 43 | 信息的表达方式决定了相关算法的能力
 44 | 
 45 | ### 4
 46 | 
 47 | IR： 信息的载体。哪些信息上船，哪些放在显眼位置。
 48 | 
 49 | 优化器能看到的只有IR，IR没有的都看不到。
 50 | 
 51 | 现在IR中允许加入各种annotation/attributes，在不改变IR的情况下加信息。就像是货运船上的集装箱。
 52 | 
 53 | 当你开始自己设计编译器的时候，或许你就可以理解 ambition 在这里的包含的感情了。
 54 | 
 55 | ### 5 - 7
 56 | 
 57 | 思维里的分析框架。
 58 | 
 59 | 这些设计的考虑，我们这门课的朋友大概有一个概念认识就行。
 60 | 
 61 | 设计的取舍需要时间，动手尝试很多组合之后，形成 **自己的经验和喜好** 。
 62 | 
 63 | ### 8
 64 | 
 65 | index slide
 66 | 
 67 | 下半部分在SDT中会讨论（存储模型在更后面）
 68 | 
 69 | ### 9
 70 | 
 71 | IR形式上的分类
 72 | 参考 EaC 书中的解释
 73 | 基本上：树AST，链3AC，混合SSA
 74 | 
 75 | ### 10
 76 | 
 77 | 直观的例子，略。
 78 | 一些前端的工作就是将左边的形式翻译成右边的形式（BytecodeBuilder 或 Generator）
 79 | 
 80 | ### 11
 81 | 
 82 | 抽象层次和数据组织形式不是统一的。
 83 | 例如解释器执行使用的字节码就比较抽象。
 84 | 
 85 | ### 12
 86 | 
 87 | 静态代码检查和程序理解一般会用到语法树
 88 | 
 89 | ### 13
 90 | 
 91 | 你遇到语法解析树的可能性比较小。
 92 | 静态代码检查和程序理解一般用AST，更简洁。
 93 | 解释器有时候也可以直接用AST计算。
 94 | 
 95 | ### 14
 96 | 
 97 | 暂时不用深究，不懂没关系，后面用到。
 98 | 
 99 | 注意这里 value 的涵义。value 是多义词。
100 | 
101 | value numbering 是一个很经典的算法。GVN基本都有实现。
102 | 
103 | ### 15
104 | 
105 | 这页内容是纯复习树的实现。
106 | 具体实现，比较简单。
107 | 二叉树和任意树转换算法看《数据结构》
108 | 
109 | ### 16
110 | 
111 | 稍微早了一点。这里是为了完整性。
112 | 
113 | 依赖关系有数据的和控制流的，这里说的是BB内，不考虑控制流。
114 | 数据的关系是通过变量之间的 def use 体现的。后面有算法寻找到 def use 关系。（这里有兴趣推荐先看看燧原科技在B站公开的基于DCC888的公开课程，里面有详细介绍。本课程后续也会详细介绍这些算法。）
115 | 
116 | ### 17
117 | 
118 | 调用图要更后一点才遇到。
119 | 体现函数/方法之间的相互关系
120 | 
121 | 提问：
122 | dep graph 节点是？，边是？
123 | CFG 的节点是？，边是？
124 | callgraph 的节点是，边是？
125 | 
126 | ### 18
127 | 
128 | di·gres·sion
129 | /ˌdīˈɡreSH(ə)n/
130 | 
131 | noun: digression; plural noun: digressions
132 | 
133 |     a temporary departure from the main subject in speech or writing.
134 | 
135 | rant
136 | /rant/
137 | 
138 | verb:
139 |     speak or shout at length in a wild, impassioned way.
140 |     "she was still ranting on about the unfairness of it all"
141 | 
142 | noun:
143 |     a spell of ranting; a tirade.
144 |     "his rants against organized religion"
145 | 
146 | 技术细节，所有的对比都应该是整数比较，为了速度。
147 | 几乎所有的VM都会对字符串进行特殊的处理。
148 | 有的会对小字符串进行特殊处理，例如40字节以内的变量名或字面量。
149 | 
150 | 后面就跟L18-IR的内容类似了。
151 | 
152 | ### 19
153 | 
154 | index page
155 | 
156 | ### 20
157 | 
158 | 三地址的地址可以理解为operand
159 | 是概念上的3地址
160 | 最多不超过3个，可以少于3个
161 | 
162 | ### 21
163 | 
164 | Quadruples 四元组 = 三地址 + opcode
165 | 所以可以有一张表格来表达
166 | 注意，数据流向是从左到右还是从右到左是喜好，没有唯一的规则。
167 | 
168 | ### 22
169 | 
170 | Triples 三元组 = 三地址 + opcode - 结果operand
171 | 隐藏的去哪里了？去到行号（序列ID）里面了。
172 | 
173 | squint
174 | /skwint/
175 | look at someone or something with one or both eyes partly closed in an attempt to see more clearly or as a reaction to strong light.
176 | 
177 | ### 23
178 | 
179 | 不确定我的理解是否正确。
180 | reorder 的是第一列，第二列不变。
181 | 
182 | ### 24 - 25
183 | 
184 | 考古：技术积累的重要过程。
185 | 计算机科学的历史很短，鼓励多阅读原始文献
186 | 
187 | ### 26
188 | 
189 | 二地址码可能就只有虚拟机里面了。
190 | X86？
191 | PDP-11 上古机型，有很多传奇可以考古
192 | 
193 | 直接搜索 destructive operations 是医学解释，
194 | 
195 | ### 27
196 | 
197 | 栈指令集，操作数的制定可以嵌入到opcode里面。
198 | 例如 multiply a b -> c 可以假设 a b 在栈上，计算后 c 压栈。
199 | 最出名的是 JavaVM。
200 | V8 解释器和 Dalvik 使用的 reg based。
201 | 
202 | 如果你感兴趣，可以找：
203 | Virtual Machine Showdown: Stack Versus Registers
204 | 
205 | ### 28
206 | 
207 | index slide
208 | 


--------------------------------------------------------------------------------
/2019-Fall/L18-IR.md:
--------------------------------------------------------------------------------
  1 | # 编译技术入门与实战
  2 | 
  3 | ## Cooper 教授 L18-IR 评注
  4 | 
  5 | ### 0 - 16
  6 | 
  7 | 复习
  8 | 
  9 | ### 17
 10 | 
 11 | 引入了BB的概念
 12 | BB引出了CFG的概念
 13 | 
 14 | ### 18
 15 | 
 16 | SSA是重要的概念。换名原则。
 17 | SSA能够极大简化某些分析。
 18 | 
 19 | A = B + 1;
 20 | A = 3 + C;
 21 | D = A + 2;
 22 | -->
 23 | A1 = B + 1;
 24 | A2 = 3 + C;
 25 | D = ??? + 2;
 26 | 
 27 | Kills 也是编译中的经典概念。
 28 | 
 29 | ### 19
 30 | 
 31 | 在汇聚点考虑 phi 节点。
 32 | 
 33 | ### 20
 34 | 
 35 | Phi 节点：存在性、最优解
 36 | 每个汇聚点对每个变量考虑phi
 37 | 有些phi可以删除掉（确定性的）
 38 | 
 39 | ### 21
 40 | 
 41 | 优劣分析，现在的我们看不懂，没关系。
 42 | 
 43 | ### 22
 44 | 
 45 | 冷知识：IR的数量大于编译器的数量
 46 | 
 47 | ### 23
 48 | 
 49 | 命名空间、or、名字空间。
 50 | 
 51 | 跳转到 slide p30 先看下。
 52 | 
 53 | ### 24
 54 | 
 55 | 注意符号表的选择和设计是经验艺术。
 56 | 初学者一般是仿照现有设计。
 57 | 可以大胆的简化，刚好够用就行。
 58 | 
 59 | ### 25
 60 | 
 61 | 现实世界各种设计规则的组合爆炸。
 62 | 还有实际程序运行中的速度和空间问题。
 63 | 
 64 | 词法作用域：在编译时刻就完成名字绑定。
 65 | 动态作用域：根据调用序列。
 66 | 
 67 | 例子：
 68 | ```C
 69 | int y;
 70 | Foo (x: int){
 71 |   return x + y;
 72 | }
 73 | 
 74 | foo(x); // use global y.
 75 | 
 76 | goo (z: int) {
 77 |   int y;
 78 |   foo(x); // ???
 79 | }
 80 | ```
 81 | 
 82 | ### 26
 83 | 
 84 | 想象一个链表。
 85 | 从最内层开始查，先查到一个就停。
 86 | C语言中的大括号构建了名字空间。
 87 | 
 88 | ### 27
 89 | 
 90 | 练习：搜索Python的相关文章。
 91 | 
 92 | defy：违反
 93 | 
 94 | ### 28
 95 | 
 96 | 实际工程化中的各种麻烦事情。
 97 | 会导致新手无法预计工作时间 ;-)
 98 | 实现细节选择特别多。最好是抄设计，参考现成的编译代码框架。
 99 | 
100 | ### 29
101 | 
102 | 在代码生成上，需要考虑名字空间，具体实现细节。
103 | 
104 | ### 30
105 | 
106 | 最后的图，一开始贴出来比较好。
107 | 


--------------------------------------------------------------------------------
/2019-Fall/L19SDT-1.md:
--------------------------------------------------------------------------------
  1 | # 编译技术入门与实战
  2 | 
  3 | ## Cooper 教授 L19SDT-1 评注
  4 | 
  5 | SDT 可以理解为 parser 给了一个搭车构建AST、符号表的机会。
  6 | 如何使用好 parser 给的 hooks，是靠经验技巧的。
  7 | 
  8 | ### 0 - 5
  9 | 
 10 | 略
 11 | 
 12 | ### 6 Example: Type System
 13 | 
 14 | 大名鼎鼎的「类型系统」。
 15 | 类型系统是什么？带有强制检查保证的契约。
 16 | 
 17 | ```C
 18 | int a; char b;
 19 | b = a; // BAD; Should fail?
 20 | string s; complex c;
 21 | s = s + c; // Depends.
 22 | ```
 23 | 
 24 | ### 7
 25 | 
 26 | 例子：名字重载
 27 | 
 28 | ```C
 29 | int i; // global
 30 | int foo() {
 31 |   int i; // function level
 32 |   {
 33 |     int i; // block
 34 |   }
 35 | }
 36 | 
 37 | ```
 38 | 
 39 | ```C++
 40 | class A { public: int i; };
 41 | class B: public A { public: int i;};
 42 | 
 43 | class A a;
 44 | class B b;
 45 | 
 46 | int main(){
 47 | 	a.i = 3;
 48 | 	b.i = 5;
 49 | 	cout<<"a.i = "<<a.i<<endl;
 50 | 	cout<<"b.i = "<<b.i<<endl;
 51 | 	class A* p = &b;
 52 | 	cout<<"p->i = "<<p->i<<endl;
 53 | }
 54 | ```
 55 | 
 56 | ### 8
 57 | 
 58 | 例子：存储布局
 59 | 这是操作系统或者修养里面会提到的知识。
 60 | 
 61 | ### 9
 62 | 
 63 | 图形化的展示下《连接器和加载器》
 64 | 或者《程序员的基本修养》
 65 | 
 66 | ### 10
 67 | 
 68 | 迷惑：为什么要在这里提这个？
 69 | 
 70 | CU = compilation unit
 71 | 
 72 | ### 11
 73 | 
 74 | linkers & loaders
 75 | 
 76 | ### 12
 77 | 
 78 | ad-hoc
 79 | 
 80 | ### 13
 81 | 
 82 | 简单版本，其实用RE就足够表示。
 83 | 
 84 | ### 14
 85 | 
 86 | 现在是判别程序，只输出 true / false。
 87 | 
 88 | ### 15 - 19
 89 | 
 90 | 接下来SDT要获得具体的整数的数值。
 91 | 
 92 | 吃进来的假设 256，先吃 2 ，再吃 5，再吃 6.
 93 | 自然的，需要一个变量/寄存器/累加器来保存
 94 | 2， 2*10+5， 25*10 + 6
 95 | 
 96 | 
 97 | ### 20 - 25
 98 | 
 99 | 对于 ACTION-GOTO 表忘记了的可以看 Parsing 部分的 slides， L14 到 L16
100 | 
101 | 9 7 6 的吃法是
102 | 9， DL(9)， DL(97) 7， DL(97)， DL(97) 6， DL(976)， Number
103 | 
104 | 
105 | ### 26
106 | 
107 | $$ 默认类型是int，也可以自己设定类型。
108 | 
109 | ### 27
110 | 
111 | 小结。
112 | 属性文法在EaC中有写。差别可能第一遍看不出来有多大。
113 | 
114 | ### 28 - 32
115 | 
116 | AHSDT = ad-hoc SDT
117 | 这里的代码骨骼是之前在Parsing部分的slides（以及书里）的内容。
118 | 


--------------------------------------------------------------------------------
/2019-Fall/L20SDT-2.md:
--------------------------------------------------------------------------------
 1 | # 编译技术入门与实战
 2 | 
 3 | ## Cooper 教授 L20SDT-2 评注
 4 | 
 5 | 上一课slides将搭车构建AST的原理介绍清楚了。
 6 | L20 开始是更加具体的构建。
 7 | 
 8 | ### 0
 9 | 
10 | SDT一共有3个slides，这是第二个。
11 | 
12 | ### 1 - 7
13 | 
14 | 复习L19的内容。注意里面有些不明白的地方的话，可以从 Cooper 教授的 Parsing-4 开始看，开始进入 handler 和 LR 部分。
15 | 
16 | ### 8
17 | 
18 | 比较重要的计算思维的理解。
19 | 也可以类比设计模式里面的算法模版。
20 | 
21 | 将【计算】附着于【语法】上
22 | Parser 决定了计算被执行的时间点和次序
23 | 可以做很多事情。
24 | 
25 | corollary - Bing dictionary
26 |     US['kɔrə.leri]UK[kə'rɒləri]
27 |     n.必然的结果（或结论）
28 |     网络推论；系；系定理
29 | 
30 | ### 9
31 | 
32 | 这里需要稍微发挥一下想象力：想象自己根据已经被具像化为自动机和栈的语法解析器（Parser）构建出来一个树结构的AST。
33 | 类似于抄作业，将概念上的语法产生式，誊抄到数据结构中的二叉树（有可能N叉，等价的）。
34 | 
35 | 一个例子：看懂了就会做之前的编程作业了。
36 | 注意 $$ 的类型
37 | 
38 | ### 10 - 19
39 | 
40 | 极好的演示，构建AST
41 | 
42 | ### 20 - 28
43 | 
44 | 即使没有看过ILOC也没关系，只要有RISC概念就能看懂。
45 | 
46 | 提到了 NextRegister，咔咔，开始硬核起来了
47 | 
48 | e·mit /əˈmit/
49 | 
50 | p26页，回忆下 IR 中的三地址码形式，隐含变量形式。
51 | 
52 | ### 29
53 | 
54 | Cooper 大佬说了啥？
55 | 大佬说啥就是啥，记下来
56 | 
57 | ### 30
58 | 
59 | 引出两个经典优化。
60 | 
61 | 主要的思想是进行任务的拆解。不要把所有要做的事情放在一个算法模版里（不好弄）。
62 | 
63 | ### 31
64 | 
65 | 先知道就行，真实世界很复杂的
66 | 
67 | ### 32
68 | 
69 | ST = 符号表
70 | 
71 | lowering 不太好翻译
72 | 
73 | 蓝字部分我也不理解，欢迎弹幕补充经验
74 | 
75 | ### 33
76 | 
77 | 字面理解好就OK。
78 | 
79 | ### 34
80 | 
81 | 符号表。先声明再使用的约定。
82 | 
83 | ### 35 - 40
84 | 
85 | 有意思的例子。
86 | 提问：LL或lR会有影响么？ Int a 和 a: int 有差别么？
87 | 


--------------------------------------------------------------------------------
/2019-Fall/L21SDT-3.md:
--------------------------------------------------------------------------------
  1 | # 编译技术入门与实战
  2 | 
  3 | ## Cooper 教授 L21SDT-3 评注
  4 | 
  5 | ### 0
  6 | 
  7 | Syntax-Driven Translation, III
  8 | 
  9 | ### 1 - 8
 10 | 
 11 | 复习，同样我们也看一遍。
 12 | 
 13 | 类型信息固定在文法里，那么新类型怎么办？
 14 | 
 15 | ```C
 16 | INT x, y, z;
 17 | struct Klass;
 18 | Klass k;
 19 | ```
 20 | 
 21 | ### 9 - 10 处理控制流
 22 | 
 23 | 一步一步添加复杂度。
 24 | 没体现的：隐式类型转换
 25 | 
 26 | ### 11
 27 | 
 28 | 这里的步骤清单很重要，仔细阅读理解下。
 29 | 
 30 | ```C
 31 | if (expr)
 32 |   cond jump to label-else
 33 | [label-then]
 34 | then Stmt;
 35 |   jump to label-exit
 36 | [label-else]
 37 | else stmt;
 38 |   jump to label-exit
 39 | [label-exit]
 40 | // next stmt
 41 | ```
 42 | 
 43 | ### 12 - 13
 44 | 
 45 | 更详细的介绍
 46 | 
 47 | ### 14
 48 | 
 49 | Bison 的支持，这种写法容易引入混乱，要慎重.
 50 | 
 51 | 符号表中的绑定也可能并不一样。
 52 | 
 53 | ### 15
 54 | 
 55 | 符号表概念复习
 56 | 
 57 | ### 16
 58 | 
 59 | 此法作用域的例子
 60 | 
 61 | ### 17
 62 | 
 63 | 类作用域的例子
 64 | 
 65 | ### 18
 66 | 
 67 | lexeme - Bing dictionary
 68 | US['leksim]UK['leksiːm]
 69 | n.词素（最小的意义单位）
 70 | 网络词位；词汇单位；语义
 71 | 
 72 | ### 19
 73 | 
 74 | storage layout 是头大的内容之一
 75 | 
 76 | ### 20
 77 | 
 78 | 先声明后使用；如果外部声明怎么办？
 79 | 
 80 | ### 21
 81 | 
 82 | 花点时间读懂语法
 83 | 
 84 | ### 22
 85 | 
 86 | （重新）引入 lifetime
 87 | 
 88 | ### 23
 89 | 
 90 | 可见性目前可以理解为符号表中的一个属性
 91 | 
 92 | ### 24
 93 | 
 94 | 这里是常识，参考C语言程序设计
 95 | 
 96 | ### 25
 97 | 
 98 | AR = 活动记录，一般就是栈帧 stack frame
 99 | 
100 | 注意不同的OSxArchxABI的组合，AR可能不一样。
101 | 
102 | ### 26
103 | 
104 | mangle - Bing dictionary
105 | US['mæŋɡ(ə)l]UK['mæŋɡ(ə)l]
106 | n.轧布机；轧板机；砑光机；碾压机
107 | v.破坏；(因发音拙劣等)使话听不懂；用轧布机砑光；乱砍
108 | 网络识别编码；矫直；钢板矫平
109 | 
110 | 在调试的时候或许会遇到。现在知道概念就行了。
111 | 
112 | ### 27
113 | 
114 | 知道概念就行
115 | 
116 | ### 28
117 | 
118 | 知道概念就行。
119 | 注意这里还有安全性问题。
120 | 
121 | ### 29
122 | 
123 | 虚拟地址空间，参考《程序员的修养》或者《操作系统原理》
124 | 
125 | ### 30
126 | 
127 | 这一页的图要记住（如果之前没有这个记忆的话），成为你的记忆。
128 | 
129 | ### 31
130 | 
131 | 参考《程序员的修养》或者《操作系统原理》
132 | 当然你不能什么基础课都不会来学编译原理 ;-)
133 | 
134 | 《C语言》 K & R
135 | 《深入理解计算机系统》
136 | 《现代操作系统》
137 | 《TCP/IP详解：卷一》
138 | 


--------------------------------------------------------------------------------
/2019-Fall/bace-lecture-01.mkv:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/2019-Fall/bace-lecture-01.mkv


--------------------------------------------------------------------------------
/2019-Fall/bace-lecture-01.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/2019-Fall/bace-lecture-01.pdf


--------------------------------------------------------------------------------
/2019-Fall/bace-lecture-02.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/2019-Fall/bace-lecture-02.pdf


--------------------------------------------------------------------------------
/2019-Fall/bace-lecture-03.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/2019-Fall/bace-lecture-03.pdf


--------------------------------------------------------------------------------
/2019-Fall/bace-lecture-04.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/2019-Fall/bace-lecture-04.pdf


--------------------------------------------------------------------------------
/2019-Fall/bace-lecture-05.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/2019-Fall/bace-lecture-05.pdf


--------------------------------------------------------------------------------
/2019-Fall/bace-lecture-06.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/2019-Fall/bace-lecture-06.pdf


--------------------------------------------------------------------------------
/2019-Fall/bace-lecture-09.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/2019-Fall/bace-lecture-09.pdf


--------------------------------------------------------------------------------
/2019-Fall/bace-lecture-10.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/2019-Fall/bace-lecture-10.pdf


--------------------------------------------------------------------------------
/2019-Fall/bace-lecture-11.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/2019-Fall/bace-lecture-11.pdf


--------------------------------------------------------------------------------
/2019-Fall/bace-lecture-12.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/2019-Fall/bace-lecture-12.pdf


--------------------------------------------------------------------------------
/2021-Spring/S03E01-Intro.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/2021-Spring/S03E01-Intro.pdf


--------------------------------------------------------------------------------
/2021-Spring/local stack slot allocation.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/2021-Spring/local stack slot allocation.pdf


--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
  1 |                                  Apache License
  2 |                            Version 2.0, January 2004
  3 |                         http://www.apache.org/licenses/
  4 | 
  5 |    TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
  6 | 
  7 |    1. Definitions.
  8 | 
  9 |       "License" shall mean the terms and conditions for use, reproduction,
 10 |       and distribution as defined by Sections 1 through 9 of this document.
 11 | 
 12 |       "Licensor" shall mean the copyright owner or entity authorized by
 13 |       the copyright owner that is granting the License.
 14 | 
 15 |       "Legal Entity" shall mean the union of the acting entity and all
 16 |       other entities that control, are controlled by, or are under common
 17 |       control with that entity. For the purposes of this definition,
 18 |       "control" means (i) the power, direct or indirect, to cause the
 19 |       direction or management of such entity, whether by contract or
 20 |       otherwise, or (ii) ownership of fifty percent (50%) or more of the
 21 |       outstanding shares, or (iii) beneficial ownership of such entity.
 22 | 
 23 |       "You" (or "Your") shall mean an individual or Legal Entity
 24 |       exercising permissions granted by this License.
 25 | 
 26 |       "Source" form shall mean the preferred form for making modifications,
 27 |       including but not limited to software source code, documentation
 28 |       source, and configuration files.
 29 | 
 30 |       "Object" form shall mean any form resulting from mechanical
 31 |       transformation or translation of a Source form, including but
 32 |       not limited to compiled object code, generated documentation,
 33 |       and conversions to other media types.
 34 | 
 35 |       "Work" shall mean the work of authorship, whether in Source or
 36 |       Object form, made available under the License, as indicated by a
 37 |       copyright notice that is included in or attached to the work
 38 |       (an example is provided in the Appendix below).
 39 | 
 40 |       "Derivative Works" shall mean any work, whether in Source or Object
 41 |       form, that is based on (or derived from) the Work and for which the
 42 |       editorial revisions, annotations, elaborations, or other modifications
 43 |       represent, as a whole, an original work of authorship. For the purposes
 44 |       of this License, Derivative Works shall not include works that remain
 45 |       separable from, or merely link (or bind by name) to the interfaces of,
 46 |       the Work and Derivative Works thereof.
 47 | 
 48 |       "Contribution" shall mean any work of authorship, including
 49 |       the original version of the Work and any modifications or additions
 50 |       to that Work or Derivative Works thereof, that is intentionally
 51 |       submitted to Licensor for inclusion in the Work by the copyright owner
 52 |       or by an individual or Legal Entity authorized to submit on behalf of
 53 |       the copyright owner. For the purposes of this definition, "submitted"
 54 |       means any form of electronic, verbal, or written communication sent
 55 |       to the Licensor or its representatives, including but not limited to
 56 |       communication on electronic mailing lists, source code control systems,
 57 |       and issue tracking systems that are managed by, or on behalf of, the
 58 |       Licensor for the purpose of discussing and improving the Work, but
 59 |       excluding communication that is conspicuously marked or otherwise
 60 |       designated in writing by the copyright owner as "Not a Contribution."
 61 | 
 62 |       "Contributor" shall mean Licensor and any individual or Legal Entity
 63 |       on behalf of whom a Contribution has been received by Licensor and
 64 |       subsequently incorporated within the Work.
 65 | 
 66 |    2. Grant of Copyright License. Subject to the terms and conditions of
 67 |       this License, each Contributor hereby grants to You a perpetual,
 68 |       worldwide, non-exclusive, no-charge, royalty-free, irrevocable
 69 |       copyright license to reproduce, prepare Derivative Works of,
 70 |       publicly display, publicly perform, sublicense, and distribute the
 71 |       Work and such Derivative Works in Source or Object form.
 72 | 
 73 |    3. Grant of Patent License. Subject to the terms and conditions of
 74 |       this License, each Contributor hereby grants to You a perpetual,
 75 |       worldwide, non-exclusive, no-charge, royalty-free, irrevocable
 76 |       (except as stated in this section) patent license to make, have made,
 77 |       use, offer to sell, sell, import, and otherwise transfer the Work,
 78 |       where such license applies only to those patent claims licensable
 79 |       by such Contributor that are necessarily infringed by their
 80 |       Contribution(s) alone or by combination of their Contribution(s)
 81 |       with the Work to which such Contribution(s) was submitted. If You
 82 |       institute patent litigation against any entity (including a
 83 |       cross-claim or counterclaim in a lawsuit) alleging that the Work
 84 |       or a Contribution incorporated within the Work constitutes direct
 85 |       or contributory patent infringement, then any patent licenses
 86 |       granted to You under this License for that Work shall terminate
 87 |       as of the date such litigation is filed.
 88 | 
 89 |    4. Redistribution. You may reproduce and distribute copies of the
 90 |       Work or Derivative Works thereof in any medium, with or without
 91 |       modifications, and in Source or Object form, provided that You
 92 |       meet the following conditions:
 93 | 
 94 |       (a) You must give any other recipients of the Work or
 95 |           Derivative Works a copy of this License; and
 96 | 
 97 |       (b) You must cause any modified files to carry prominent notices
 98 |           stating that You changed the files; and
 99 | 
100 |       (c) You must retain, in the Source form of any Derivative Works
101 |           that You distribute, all copyright, patent, trademark, and
102 |           attribution notices from the Source form of the Work,
103 |           excluding those notices that do not pertain to any part of
104 |           the Derivative Works; and
105 | 
106 |       (d) If the Work includes a "NOTICE" text file as part of its
107 |           distribution, then any Derivative Works that You distribute must
108 |           include a readable copy of the attribution notices contained
109 |           within such NOTICE file, excluding those notices that do not
110 |           pertain to any part of the Derivative Works, in at least one
111 |           of the following places: within a NOTICE text file distributed
112 |           as part of the Derivative Works; within the Source form or
113 |           documentation, if provided along with the Derivative Works; or,
114 |           within a display generated by the Derivative Works, if and
115 |           wherever such third-party notices normally appear. The contents
116 |           of the NOTICE file are for informational purposes only and
117 |           do not modify the License. You may add Your own attribution
118 |           notices within Derivative Works that You distribute, alongside
119 |           or as an addendum to the NOTICE text from the Work, provided
120 |           that such additional attribution notices cannot be construed
121 |           as modifying the License.
122 | 
123 |       You may add Your own copyright statement to Your modifications and
124 |       may provide additional or different license terms and conditions
125 |       for use, reproduction, or distribution of Your modifications, or
126 |       for any such Derivative Works as a whole, provided Your use,
127 |       reproduction, and distribution of the Work otherwise complies with
128 |       the conditions stated in this License.
129 | 
130 |    5. Submission of Contributions. Unless You explicitly state otherwise,
131 |       any Contribution intentionally submitted for inclusion in the Work
132 |       by You to the Licensor shall be under the terms and conditions of
133 |       this License, without any additional terms or conditions.
134 |       Notwithstanding the above, nothing herein shall supersede or modify
135 |       the terms of any separate license agreement you may have executed
136 |       with Licensor regarding such Contributions.
137 | 
138 |    6. Trademarks. This License does not grant permission to use the trade
139 |       names, trademarks, service marks, or product names of the Licensor,
140 |       except as required for reasonable and customary use in describing the
141 |       origin of the Work and reproducing the content of the NOTICE file.
142 | 
143 |    7. Disclaimer of Warranty. Unless required by applicable law or
144 |       agreed to in writing, Licensor provides the Work (and each
145 |       Contributor provides its Contributions) on an "AS IS" BASIS,
146 |       WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147 |       implied, including, without limitation, any warranties or conditions
148 |       of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149 |       PARTICULAR PURPOSE. You are solely responsible for determining the
150 |       appropriateness of using or redistributing the Work and assume any
151 |       risks associated with Your exercise of permissions under this License.
152 | 
153 |    8. Limitation of Liability. In no event and under no legal theory,
154 |       whether in tort (including negligence), contract, or otherwise,
155 |       unless required by applicable law (such as deliberate and grossly
156 |       negligent acts) or agreed to in writing, shall any Contributor be
157 |       liable to You for damages, including any direct, indirect, special,
158 |       incidental, or consequential damages of any character arising as a
159 |       result of this License or out of the use or inability to use the
160 |       Work (including but not limited to damages for loss of goodwill,
161 |       work stoppage, computer failure or malfunction, or any and all
162 |       other commercial damages or losses), even if such Contributor
163 |       has been advised of the possibility of such damages.
164 | 
165 |    9. Accepting Warranty or Additional Liability. While redistributing
166 |       the Work or Derivative Works thereof, You may choose to offer,
167 |       and charge a fee for, acceptance of support, warranty, indemnity,
168 |       or other liability obligations and/or rights consistent with this
169 |       License. However, in accepting such obligations, You may act only
170 |       on Your own behalf and on Your sole responsibility, not on behalf
171 |       of any other Contributor, and only if You agree to indemnify,
172 |       defend, and hold each Contributor harmless for any liability
173 |       incurred by, or claims asserted against, such Contributor by reason
174 |       of your accepting any such warranty or additional liability.
175 | 
176 |    END OF TERMS AND CONDITIONS
177 | 
178 |    APPENDIX: How to apply the Apache License to your work.
179 | 
180 |       To apply the Apache License to your work, attach the following
181 |       boilerplate notice, with the fields enclosed by brackets "[]"
182 |       replaced with your own identifying information. (Don't include
183 |       the brackets!)  The text should be enclosed in the appropriate
184 |       comment syntax for the file format. We also recommend that a
185 |       file or class name and description of purpose be included on the
186 |       same "printed page" as the copyright notice for easier
187 |       identification within third-party archives.
188 | 
189 |    Copyright [yyyy] [name of copyright owner]
190 | 
191 |    Licensed under the Apache License, Version 2.0 (the "License");
192 |    you may not use this file except in compliance with the License.
193 |    You may obtain a copy of the License at
194 | 
195 |        http://www.apache.org/licenses/LICENSE-2.0
196 | 
197 |    Unless required by applicable law or agreed to in writing, software
198 |    distributed under the License is distributed on an "AS IS" BASIS,
199 |    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200 |    See the License for the specific language governing permissions and
201 |    limitations under the License.
202 | 


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
 1 | # 编译技术入门与实战公开课
 2 | 
 3 | ## 2021 春季 编译技术入门与实战·第三期
 4 | 
 5 | 编译技术入门与实战·第三期·2021春季（连载中）
 6 | https://www.bilibili.com/video/bv14b4y1X7uX
 7 | 
 8 | ## 2020 秋季 本学期课程更名为 **PLCT编译器设计讨论班（2020秋）**
 9 | 
10 | 每周五、周六的下午3点到4点之间进行讨论课，线上腾讯会议的形式，欢迎加入讨论。进入方式是添加我（lazyparser）的微信 lazyparser （备注编译课程）进入微信学习群，每次会议的通知会在群里发出来。以及一些资源也会在群里贴出。
11 | 
12 | - 第16次讨论：RISC-V ABI 介绍 by 林思南 [video](https://www.bilibili.com/video/BV1bz4y1S71o)
13 | - 第15次讨论：GCC入门（二）RTL by 陈嘉炜 [video](https://www.bilibili.com/video/BV1gy4y1H7bg)
14 | - 第14次讨论：上手开发GCC-陈嘉炜 [video](https://www.bilibili.com/video/BV1Nf4y1y7Bz)
15 | - 第13次讨论：RVV-LLVM设计、shecc代码、RISCV反汇编器、EEMBC [video](https://www.bilibili.com/video/BV1Uz4y1r7sq)
16 | - 第12次讨论：LLVM栈对齐、shecc libc、zfinx gdb反汇编支持 [video](https://www.bilibili.com/video/BV1AT4y1u7ys)
17 | - 第11次讨论：LLVM寄存器表示、RISC-V指令集学习方法 [video](https://www.bilibili.com/video/BV1kp4y1z7JU)
18 | - 第10次讨论：RV32Emu-Next [video](https://www.bilibili.com/video/BV1nv411r7yf)
19 | - 第09次讨论：LLVM GlobalISel、RISC-V Zfinx GNU Impl [video](https://www.bilibili.com/video/BV1iz4y1y7Xe)
20 | - 第08次讨论：OpenJ9、LLVM、RISC-V、Zfinx [video](https://www.bilibili.com/video/BV1hv411r7ns)
21 | - 第07次讨论：为 rvv-llvm 添加一个 intrinsic (廖春玉) [video](https://www.bilibili.com/video/bv1PA411j79G)
22 | - 第06次讨论：指令选择、Zfinx、MIT作业 [video](https://www.bilibili.com/video/BV1Tz4y1y7Ng)
23 | - 第05次讨论：Tiger编译器RISC-V后端、MLIR运行GEMM在蜂鸟FPGA评估版上 [video](https://www.bilibili.com/video/BV14t4y1e7nJ)
24 | - 第04次讨论：Register Scavenger、编译优化简介 [video](https://www.bilibili.com/video/BV1Qt4y1Y7yc)
25 | - 第03次讨论：LLVM、SDT、作业 [video](https://www.bilibili.com/video/bv1Ky4y1879o)
26 | - 第02次讨论：EaC ch4、LLVM IR、shecc 教学编译器 [video](https://www.bilibili.com/video/BV1zA41177SH)
27 | - 第01次讨论：《编译器设计》前三章回顾 [video](https://www.bilibili.com/video/BV1454y1m7EF)
28 | 
29 | ## 2019 秋季
30 | 
31 | 编译器入门课程的配套教学资料
32 | 
33 | 视频课程正在持续更新，请根据自己的节奏进行学习。
34 | 
35 | 编译技术是一门工匠艺术，一定是需要动手编程才能学会的。刚看 slides 和视频是不够的， fork 以下的 codes 仓库，围观六位助教学生的代码实现，并将你自己的代码上传到 GitHub 吧 ❤️
36 | 
37 | https://github.com/lazyparser/becoming-a-compiler-engineer-codes
38 | 
39 | 所有的课程视频可以通过以下入口访问，后续课程会通过增加分p的方式陆续上传：
40 | 
41 | https://www.bilibili.com/video/av78503049
42 | 
43 | 本仓库地址是
44 | 
45 | https://github.com/lazyparser/becoming-a-compiler-engineer
46 | 
47 | 计划更新至2020年8月(受到COVID-19影响延长2个月)。
48 | 
49 | 可以参考的学生作业
50 | 
51 | https://github.com/wenwensong114/scanner
52 | 
53 | 可以参考的教材：
54 | 
55 | https://pandolia.net/tinyc/index.html
56 | 偏实战，用简单和易于实现的实例来描述基本的编译原理及过程
57 | 


--------------------------------------------------------------------------------
/doc/Makefile:
--------------------------------------------------------------------------------
 1 | # Minimal makefile for Sphinx documentation
 2 | #
 3 | 
 4 | # You can set these variables from the command line.
 5 | SPHINXOPTS    =
 6 | SPHINXBUILD   = sphinx-build
 7 | SPHINXPROJ    = bace
 8 | SOURCEDIR     = .
 9 | BUILDDIR      = _build
10 | 
11 | RM = rm -rf
12 | 
13 | # Put it first so that "make" without argument is like "make help".
14 | help:
15 | 	@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
16 | 
17 | doc:
18 | 	$(MAKE) html latexpdf
19 | 
20 | clean:
21 | 	$(RM) $(BUILDDIR)
22 | 
23 | .PHONY: help Makefile clean
24 | 
25 | # Catch-all target: route all unknown targets to Sphinx using the new
26 | # "make mode" option.  $(O) is meant as a shortcut for $(SPHINXOPTS).
27 | %: Makefile
28 | 	@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
29 | 


--------------------------------------------------------------------------------
/doc/bace lecture.rst:
--------------------------------------------------------------------------------
  1 | =======================================
  2 | 《方舟·编译技术入门与实战》 讲义
  3 | =======================================
  4 | 
  5 | 
  6 | 第一章 课程介绍
  7 | ==================
  8 | 
  9 | 
 10 | 关于课程直播
 11 | ---------------
 12 | 
 13 | 错过直播没关系,所有直播都有回看
 14 | 
 15 | - 课程配套代码及幻灯片地址(也是提问的地方)
 16 | 
 17 |   https://github.com/lazyparser/becoming-a-compiler-engineer
 18 | 
 19 |   https://github.com/lazyparser/becoming-a-compiler-engineer-codes 
 20 | 
 21 | - 课程视频回看(包含所有直播及录播视频)
 22 | 
 23 |   https://space.bilibili.com/296494084
 24 | 
 25 | - 课程直播地址(可以弹幕或评论区互动)
 26 | 
 27 |   https://live.bilibili.com/10339607
 28 | 
 29 | 
 30 | 主讲人介绍
 31 | --------------
 32 | 
 33 | 吴伟(@lazyparser)
 34 | 
 35 | - HelloGCC & HelloLLVM 社区负责人
 36 | - 软件所PLCT实验室项目总监(Group Lead)
 37 | - 本次课程的组织者和主要讲师
 38 | 
 39 | 
 40 | 关于本课程
 41 | --------------
 42 | 
 43 | 这是一门什么样的课程?为何要做成慕课?
 44 | +++++++++++++++++++++++++++++++++++++++++
 45 | 
 46 | - 面向编译器从业人员(新人)的入门培训课程
 47 | - 包含了我的编译团队新人培养的完整内容
 48 | - 现有的编译原理慕课构成了完整内容的一小部分
 49 | - PLCT有2名新人和5位实习生跟大家同步接受培训
 50 | - 希望帮助更多小伙伴平缓迈进编译技术领域
 51 | 
 52 | 
 53 | 已经有很多慕课了。为什么要重复开课?
 54 | +++++++++++++++++++++++++++++++++++++++++
 55 | 
 56 | - 目标和定位不同:这是编译器从业者的入门培训
 57 | - 覆盖内容不同:轻理论,侧重中后端编程实践
 58 | - 充分利用已有的慕课资源,不做重复工作(结合SSR模式,后介绍)
 59 | - 引论部分直接以冯博琴老师、王挺老师等公开课作为学习材料
 60 | - 前端理论部分以 Keith Cooper、Hal Perkins、冯博琴老师等作为学习材料
 61 | 
 62 | 
 63 | 充分利用已有的慕课资源
 64 | +++++++++++++++++++++++++
 65 | 
 66 |   https://www.clear.rice.edu/comp412/
 67 | 
 68 |   https://courses.cs.washington.edu/courses/csep501/08wi/
 69 | 
 70 |   https://www.bilibili.com/video/av9946063
 71 | 
 72 |   https://www.bilibili.com/video/av59119931
 73 | 
 74 | 
 75 | 课程涵盖的内容有哪些?
 76 | +++++++++++++++++++++++
 77 | 
 78 | - 编译器基础理论知识及算法原理
 79 | - Clang/LLVM 框架的使用与开发(以RISC-V后端为例)
 80 | - GNU GCC 的实现分析与对比(以RISC-V和C-SKY后端为例)
 81 | - 方舟编译框架的实现分析与RISC-V后端支持
 82 | 
 83 | 
 84 | 课程侧重的内容有哪些?
 85 | +++++++++++++++++++++++++
 86 | 
 87 | .. image:: ./images/image01.png
 88 | 
 89 | 
 90 | 学完课程之后掌握的能力
 91 | +++++++++++++++++++++++++
 92 | 
 93 | - 根据语言定义,能够基于LLVM等开源框架实现对应的编译器
 94 | - 能够对应用程序进行更加准确的瓶颈分析和性能优化
 95 | - 调试程序更快,心态更平和
 96 | 
 97 | 
 98 | 面向哪些群体?我适合学习么?
 99 | ++++++++++++++++++++++++++++
100 | 
101 | - 程序员或即将成为程序员的在校生
102 | 
103 |   视频及课件特别考虑了手机屏幕观看,方便上下班通勤时学习
104 | 
105 | - 需要掌握计算机专业的基础理论,能够自学补充所需知识
106 | 
107 |   不需要编译背景,在这方面可以是零基础
108 | 
109 | - 熟练C/C++/Java中一种,平时有写代码
110 | 
111 | 
112 | 我数学不好,能学会这门课么?
113 | +++++++++++++++++++++++++++
114 | 
115 | - 能。发挥主观能动性,哪里不会问哪里
116 | 
117 | - 在视频评论区评论或在 GitHub issues 里提问
118 | 
119 |   * 我和TA后续会在评论区和issues中进行解答
120 | 
121 |   * 一对一问答属于企业付费咨询,默认请在社区中公开提问
122 | 
123 | 
124 | 我英语不好,能学好这门课么?
125 | +++++++++++++++++++++++++++
126 | 
127 | - 能。英语好不好是主观自我评价。没什么问题
128 | 
129 | - 计算机领域的句型相对固定,常用术语约几百个
130 | 
131 | 
132 | 大概需要多长时间学完?
133 | +++++++++++++++++++++++
134 | 
135 | - 按照新人培训半年的时间做的内容安排
136 | 
137 |   也可以按照自己时间节奏来安排,贵在坚持
138 | 
139 | - 每周2~3个课时(直播/录播)
140 | 
141 |   我会尽量拆分成20分钟左右,可以在上下班通勤的时候看
142 | 
143 | - 每周6~10个小时写代码
144 | 
145 |   这是必须的,视频可以不看,代码一定要自己写
146 | 
147 | 参考的教材有哪些?
148 | ++++++++++++++++++++
149 | 
150 | .. image:: ./images/image02.png
151 |   :width: 200
152 | 
153 | .. image:: ./images/image03.png
154 |   :width: 200
155 | 
156 | .. image:: ./images/image04.png
157 |   :width: 200
158 | 
159 | 
160 | 课程与方舟编译框架是什么关系?
161 | ++++++++++++++++++++++++++++++++++
162 | 
163 | - (动机)HelloGCC & HelloLLVM社区希望推动方舟的发展
164 | 
165 |   与方舟开源社区一起推动国内编译技术的发展与人才的培养
166 | 
167 | - (内容)为方舟开源编译器提供RISC-V后端支持
168 | 
169 |   依赖于方舟编译器2020年上半年的开源进度
170 | 
171 | 
172 | 方舟开源编译框架的介绍和后续路线图
173 | +++++++++++++++++++++++++++++++++++++
174 | 
175 | 史宁宁(小乖他爹)已经做了一期梳理的视频
176 | 
177 | https://www.bilibili.com/video/av78179578
178 | 
179 | 
180 | .. image:: ./images/image05.png
181 |   :width: 400
182 | 
183 | 
184 | 学完会有证书么?
185 | +++++++++++++++++
186 | 
187 | - 单纯观看课程(旁听)没有证书或记录
188 | - 完成课程项目作业之后可以将自己名字加入课程的学分名单中
189 | - 能力相互认证的申请是独立的,完成为期三天的现场考核之后获得
190 | 
191 | 
192 | 后续教学会如何组织?
193 | +++++++++++++++++++++
194 | 
195 | - SSR模式:独立学习、课堂讨论、研究点探索
196 | 
197 |   inherit from 刘道玉先生
198 | 
199 | - 课堂讨论拟采用微信群+邮件列表形式
200 | 
201 |   共有7次左右讨论题目
202 | 
203 | - 作业通过GitHub提交
204 | 
205 |   https://github.com/lazyparser/becoming-a-compiler-engineer
206 | 
207 | 
208 | 会有客座讲座么?
209 | +++++++++++++++++++
210 | 
211 | - 有。课堂讨论和研究探索部分会大量邀请客座讲座
212 | - 会邀请PLCT的同事来做技术专题讲座
213 | - 计划邀请社区活跃的专家来分享最新的成果
214 | 
215 | 
216 | 用什么编程语言讲解?
217 | +++++++++++++++++++++++
218 | 
219 | - 大量使用C
220 | - 少数场合使用C++和Java
221 | 
222 | 下次课程内容:词法解析
223 | ++++++++++++++++++++++++
224 | 
225 | 引论部分的自学资料(请在下次课程前自学):
226 | 
227 |   https://www.bilibili.com/video/av59119931?p=1
228 | 
229 |   https://www.bilibili.com/video/av59119931?p=2
230 | 
231 |   https://www.bilibili.com/video/av9946063?p=1
232 | 
233 |   https://www.bilibili.com/video/av9946063?p=2
234 | 
235 | 
236 | 加入本课程的旁听学习群
237 | +++++++++++++++++++++++++++
238 | 
239 | 群有人数限制,满员后请在HelloGCC微信公众号输入「旁听」
240 | 
241 | .. image:: ./images/image06.png
242 |   :width: 200
243 | 
244 | 
245 | .. image:: ./images/image07.png
246 |   :width: 200
247 | 
248 | 
249 | 
250 | 
251 | 第二章 词法分析
252 | ====================
253 | 
254 | 
255 | 关于课程直播
256 | ---------------
257 | 
258 | 错过直播没关系,所有直播都有回看
259 | 
260 | - 课程配套代码及幻灯片地址(也是提问的地方)
261 | 
262 |   https://github.com/lazyparser/becoming-a-compiler-engineer
263 | 
264 |   https://github.com/lazyparser/becoming-a-compiler-engineer-codes 
265 | 
266 | - 课程视频回看(包含所有直播及录播视频)
267 | 
268 |   https://space.bilibili.com/296494084
269 | 
270 | - 课程直播地址(可以弹幕或评论区互动)
271 | 
272 |   https://live.bilibili.com/10339607
273 | 
274 | 
275 | 主讲人介绍
276 | --------------
277 | 
278 | 吴伟(@lazyparser)
279 | 
280 | - HelloGCC & HelloLLVM 社区负责人
281 | - 软件所PLCT实验室项目总监(Group Lead)
282 | - 本次课程的组织者和主要讲师
283 | 
284 | 
285 | 本次课程的内容
286 | -------------------
287 | 
288 | - 第一节课课后作业的复习（包含一些元学习理论知识）
289 | - 词法分析：知识地图、算法、可视化工具（很好玩）
290 | - 几个必要的数学概念的补充（不要怕）
291 | - 前端编程练习用语言PL/0的准备
292 | 
293 | 
294 | 你会使用到的资源（课后阅读一定要完成）
295 | 
296 |   https://www.clear.rice.edu/comp412/ Keith Cooper老师
297 | 
298 |   https://courses.cs.washington.edu/courses/csep501/08wi/ Hal Perkins老师
299 | 
300 |   https://www.bilibili.com/video/av9946063 冯博琴老师
301 | 
302 |   https://www.bilibili.com/video/av59119931 王挺老师
303 | 
304 | 
305 | 
306 | 第一节课课后作业的复习（包含一些元学习理论知识）
307 | +++++++++++++++++++++++++++++++++++++++++++++++++++
308 | 
309 | 上周课后作业的复习
310 | *********************
311 | 
312 |   引论部分的自学资料（请在下次课程前自学）：
313 | 
314 |   https://www.bilibili.com/video/av59119931?p=1
315 | 
316 |   https://www.bilibili.com/video/av59119931?p=2
317 | 
318 |   https://www.bilibili.com/video/av9946063?p=1
319 | 
320 |   https://www.bilibili.com/video/av9946063?p=2
321 | 
322 | 
323 | 上周的课后阅读，建立了整体概念
324 | **********************************
325 | 
326 |   以冯博琴老师的公开课为例:
327 | 
328 | .. image:: ./images/image08.png
329 |   :width: 350
330 | 
331 | .. image:: ./images/image09.png
332 |   :width: 350
333 | 
334 | .. image:: ./images/image10.png
335 |   :width: 350
336 | 
337 | .. image:: ./images/image11.png
338 |   :width: 350
339 | 
340 | .. image:: ./images/image12.png
341 |   :width: 350
342 | 
343 | .. image:: ./images/image13.png
344 |   :width: 350
345 | 
346 | .. image:: ./images/image14.png
347 |   :width: 350
348 | 
349 | 
350 | 四个老师，为什么第一课都是总体介绍？
351 | **************************************
352 | 
353 | - 不管是国内还是国外的编译老师，都先讲编译器的总体架构
354 | - 进一步的，每个领域的课程系列，第一课都是 big picture
355 | 
356 |   （还没完成上周课后阅读作业的同学请本周完成）
357 | 
358 | 
359 | 学习的方法：建立自己的知识地图
360 | **********************************
361 | 
362 | - 这不是某位授课老师的发明创意；这是教育和认知科学的成果
363 | - 进入新的领域，最有效率的方法之一是快速建立知识地图
364 | - 在熟悉的领域内工作，可以看成不断扩展地图边界的过程
365 | 
366 | 
367 | 对于成年人而言，掌握学习方法论尤为重要
368 | *****************************************
369 | 
370 | - 本课程的学习者，大多已经成年，有着各类条件约束
371 | 
372 |   - 有限的时间、有限的注意力、有限的体力
373 |   - 多线任务，有时候不太合乎情理的项目交付 Deadline
374 | 
375 | - 学会如何快速学习是我作为新人培训人员希望新人达到的目标
376 | 
377 |   - 学习的方法论能够让我们在尽可能短时间内高质量地获得知识能力
378 | 
379 | 知识地图的作用
380 | ****************
381 | 
382 | - 增加面对未知情况做决策时的自信，缩小风险的概率区间
383 | - 有计划的自我激励，避免从学习区进入恐慌区（Panic Zone）
384 | - 认清自己的工作是工程还是研究
385 | 
386 |   - SSR中的R一般是在人类知识地图边界处
387 | 
388 | 
389 | .. image:: ./images/image15.png
390 |   :width: 200
391 | 
392 | 
393 | 看英文资料时候的注意事项（不要怕/逃）
394 | *****************************************
395 | 
396 | - 重要的心理门槛：念出单词正确的发音（价值百万的培训点）
397 | - 术语直接随手查词典（从下周开始基本上都是英文资料了）
398 | 
399 |   - 大量在线免费词典，例如 https://dict.youdao.com
400 | 
401 | - 人名不会念很正常
402 | 
403 |   - 发音不一定是英语，要问；初次见面一定要问对方
404 | 
405 | - 公司组内或公开报告前确保查询过所有出现单词
406 | 
407 |   - 否则现场时候心态很可能因为单词发音不确定紧张到崩
408 | 
409 | 
410 | 
411 | 词法分析：知识地图、算法、可视化工具（很好玩）
412 | ++++++++++++++++++++++++++++++++++++++++++++++++
413 | 
414 | 词法分析：自学 Cooper 教授课件的 1 – 8 
415 | ********************************************
416 | 
417 | https://www.clear.rice.edu/comp412/Lectures/
418 | 
419 | 
420 | .. image:: ./images/image16.png
421 |   :width: 500
422 | 
423 | 
424 | 词法分析：（复习）在编译器整体架构中的位置
425 | ********************************************
426 | 
427 | .. image:: ./images/image17.png
428 |   :width: 500
429 | 
430 | 
431 | 记住这一页
432 | **************
433 | 
434 | 记住了，理论部分就全部都不会忘了
435 | 
436 | .. image:: ./images/image18.png
437 |   :width: 500
438 | 
439 | 
440 | 有了这张图，就不会忘记了
441 | 
442 | .. image:: ./images/image19.png
443 |   :width: 500
444 | 
445 | 提问：有 minNFA 么？为什么没画？
446 | 
447 | 
448 | 记住这张图
449 | *************
450 | 
451 | .. image:: ./images/image20.png
452 |   :width: 500
453 | 
454 | 
455 | 作业：查如何发音
456 | 
457 | - nondeterministic
458 | - finite
459 | - automaton
460 | - paths
461 | - final
462 | - Brozozowski
463 | - Hopcroft
464 | - union
465 | 
466 | 
467 | 词法分析几个算法的掌握程度
468 | ****************************
469 | 
470 | - 要求掌握正则表达式的概念和写法
471 | 
472 |   - 不同的语言/工具可能有不同的表示法，需要注意细节
473 | 
474 | - 能够手工构造 RE to NFA、NFA to DFA
475 | 
476 |   - 能够理解 DFA to min DFA 的算法思想
477 | 
478 | - 其它算法实现细节及练习，以后工作中用到的时候再回来做
479 | 
480 |   - 知识地图：你知道算法在这里，有开源实现，知道自己能重新实现
481 | 
482 | 
483 | 使用工具：正确性验证、可视化
484 | *****************************
485 | 
486 | .. image:: ./images/image21.png
487 |   :width: 500
488 | 
489 | 
490 | 
491 | https://jex.im/regulex
492 | 
493 | .. image:: ./images/image22.png
494 |   :width: 500
495 | 
496 | https://cyberzhg.github.io/toolbox/regex2nfa
497 | 
498 | .. image:: ./images/image23.png
499 |   :width: 500
500 | 
501 | https://cyberzhg.github.io/toolbox/min_dfa
502 | 
503 | .. image:: ./images/image24.png
504 |   :width: 500
505 | 
506 | https://cyberzhg.github.io/toolbox/nfa2dfa
507 | 
508 | .. image:: ./images/image25.png
509 |   :width: 500
510 | 
511 | https://cyberzhg.github.io/toolbox
512 | 
513 | .. image:: ./images/image26.png
514 |   :width: 500
515 | 
516 | https://regexr.com/
517 | 
518 | .. image:: ./images/image27.png
519 |   :width: 500
520 | 
521 | http://ivanzuzak.info/noam/webapps/fsm_simulator/
522 | 
523 | .. image:: ./images/image28.png
524 |   :width: 500
525 | 
526 | .. image:: ./images/image29.png
527 |   :width: 500
528 | 
529 | 
530 | 课后作业（词法分析部分）
531 | *************************
532 | 
533 | - 学习 Cooper 的课件（幻灯片）
534 | 
535 |   - 不明白的地方在我们课程的repo/issues里面提问，我会回答
536 |   - 看完之后阅读/观看另外三位老师的课程，查缺补漏
537 | 
538 | - 玩一玩推荐的这几个可视化演示的小站点
539 | 
540 |   - 多数是GitHub开源的，直接看到算法的源代码
541 |   - 如果寻找到好玩的可视化的站点欢迎开issues推荐
542 | 
543 | 
544 | 
545 | 几个必要的数学概念的补充（不要怕）
546 | +++++++++++++++++++++++++++++++++++
547 | 
548 | - 我们这门课程里面说的数学，包含哪些东西？
549 | - 问题的定义和解空间的确定
550 | - 解的存在性
551 | - 解的构造算法、找到最优解的算法
552 | - 数学解法通过计算机程序实现的问题
553 | 
554 |   （现在不理解不影响学习；后续遇到具体的例子会再解释）
555 | 
556 | 
557 | 我们这门课程里面说的数学，是个大杂烩
558 | **************************************
559 | 
560 | - 命题逻辑：如果p成立可以推出q成立，q推导r，那么p->r
561 | - 数学建模：建立一个模型然后在模型中推导
562 | - 形式语言与自动机理论、计算理论
563 | - 整数规划、最优化方法等
564 | - 其它我也尚未理解的数学领域（部分优化使用到了）
565 | 
566 |   （这一小节听不懂没关系，是我没讲清楚还没有找到更简单的方式，后续我会继续再遇到的时候再次详细说明）
567 | 
568 | 
569 | 物理世界-> 数学世界-> 物理世界
570 | *******************************
571 | 
572 | - 物理世界的属性和关系进行抽象，得到一个概念上的模型
573 | 
574 |   - 例如CPU抽象成编译器中微架构的表示，编程不同部件之间的图
575 | 
576 | - 在模型上，通过一些计算法则和约束条件，推演得到结论
577 | 
578 |   - 例如CPU被抽象之后，可以调度和排序出在模型中速度最快的代码序列
579 | 
580 | - 将模型中的结论映射回物理世界，验证是否满足要求
581 | 
582 |   - 不断修改模型也是预期中的工作，不可能一下子就完美
583 | 
584 | 
585 | 数学模型有可能不对，映射到数学模型，尤其是你自己写的，需要不断调整
586 | 
587 | .. image:: ./images/image30.png
588 |   :width: 300
589 | 
590 | 
591 | 解的空间和解的存在性
592 | ***********************
593 | 
594 | - 具体问题抽象成模型之后，所有可能的答案构成了一个集合/空间
595 | 
596 |   - 例：二维平面上的所有点
597 |   - 例：所有的正则表达式
598 |   - 例：一个编译器所有的参数组合
599 | 
600 | - 给出一个目标，是否存在一个答案（解）能够满足这个目标？
601 | 
602 |   - 是否有一个点，即落于线段A、又落于线段B上？
603 |   - 是否存在一个正则表达式，能够识别字符串集合A，并拒绝字符串集合B？
604 | 
605 | 
606 | 找到解的算法、寻找最优的解、验证最优解
607 | ****************************************
608 | 
609 | - 解决了解的存在性的问题之后，接下来就是如何找到这个（些）解
610 | 
611 |   - 穷举法如果能work，问题都好说
612 |   - 构造法是另一种常见算法
613 |   - 其它方法就比较难了：各种各样的搜索法
614 | 
615 | - 最优解
616 | 
617 |   - 给定一些约束条件，一个目标，在可行解中找目标最大化的解
618 |   - 数学性质好的解空间可以构造、搜索、逼近；不好的主要是搜索或近似解
619 |   - 贪婪法、动态规划、剪枝查找、模拟退火、启发式算法……
620 | 
621 | - 连续空间和离散空间
622 | 
623 |   - 数学性质（连续性、可微性）不好的离散空间比较难搞
624 |   - 编译器中后端算法中存在大量的离散空间模型，后续会逐步说明
625 | 
626 | - 验证最优解
627 | 
628 |   - 一般而言，验证一个解是最优的，比找到这个最优解要容易（不会更难）
629 |   - 在真实的工程场景中，验证最优解有时候也不容易
630 |   - 一般性的，是有一个「差不多可以当作最优解接受」的范围
631 | 
632 | 
633 | 数学算法变成计算机代码
634 | ***************************
635 | 
636 | - 数字的有效范围和精度范围问题，至今仍是一大类安全隐患
637 | - 算法的时间复杂度（后续每个后端算法都会有说明）
638 | - 算法的空间复杂度（后续每个后端算法都会有说明）
639 | - 数学模型跟真实世界之间的映射关系的精确程度：大量的取舍
640 | 
641 | 一些可以当作知识点记忆的内容
642 | ******************************
643 | 
644 | - 编译器中大量算法处理的是离散空间的最优解问题
645 | - 大量的问题是NP的；也就是说没有多项式时间的解法
646 | - 因此，编译器中大量使用启发式算法寻找近似解
647 | 
648 |   - 启发式（Heuristic）就是「专家的猜测」
649 | 
650 | 
651 | 前端编程练习用语言PL/0的准备
652 | ++++++++++++++++++++++++++++++++++
653 | 
654 | PL/0 是什么？一个用于编译器教学的语言
655 | ****************************************
656 | 
657 | - https://en.wikipedia.org/wiki/PL/0
658 | 
659 |   - 这里有完整的语法和历史介绍，阅读这一个网页就可以进行下一步练习了
660 |   - 里面提供了一些例子，可以用于前一小节RE的测试中
661 | 
662 | - 理论上图灵完备
663 | 
664 |   - 实际上受限于可编写的程序的规模（跟C++之父为什么要发明C++同样原因）
665 | 
666 | 
667 | 为什么我们要用 PL/0
668 | **********************
669 | 
670 | - 我们的课程包含了前端的实现练习，需要一个语言规范
671 | 
672 |   - 可选范围：PL/0、Tiger、C、C++、Java、Python、Ruby
673 | 
674 | - 同时，前端并不是我们本次课程重点，需要一个简单的语言
675 | 
676 |   - 可选范围： PL/0、Tiger、C、C++、Java、Python、Ruby
677 | 
678 | - 我们是自学+指导的慕课SSR教学模式，最好用有大量的资料
679 | 
680 |   - 可选范围： PL/0、Tiger（有防作弊需要）、C、C++、Java、Python、Ruby
681 | 
682 | 
683 | 在GitHub上搜索 PL0 ：大量学习资料
684 | *************************************
685 | 
686 | .. image:: ./images/image31.png
687 |   :width: 500
688 | 
689 | 
690 | 我们会怎么用 PL/0 来帮助学习
691 | *********************************
692 | 
693 | - 根据语言规范，用 flex/bison 实现词法分析和语法分析
694 | - 翻译到 LLVM IR，用这个过程学习 LLVM IR 的操作
695 | - 掌握后，你可以在工作中自己创造新的语言，DSL或通用都可以
696 | 
697 | 课后练习（PL/0部分）
698 | *********************
699 | 
700 | - 阅读 PL/0 的语言规范，尝试自己手写几个例子
701 | - 用之前小节提到的可视化工具尝试用RE实现词法分析的匹配部分
702 | - 从GitHub或者gitee上找一些参考的例子，看一看
703 | - 预习 flex 这个工具的语法及使用，跑个例子
704 | 
705 | 
706 | 第三章 实验起步
707 | ====================
708 | 
709 | 关于课程直播
710 | ---------------
711 | 
712 | 错过直播没关系，所有直播都有回看
713 | 
714 | - 课程配套代码及幻灯片地址(也是提问的地方)
715 | 
716 |   https://github.com/lazyparser/becoming-a-compiler-engineer
717 | 
718 |   https://github.com/lazyparser/becoming-a-compiler-engineer-codes 
719 | 
720 | - 课程视频回看(包含所有直播及录播视频)
721 | 
722 |   https://space.bilibili.com/296494084
723 | 
724 | - 课程直播地址(可以弹幕或评论区互动)
725 | 
726 |   https://live.bilibili.com/10339607
727 | 
728 | 
729 | 主讲人介绍
730 | --------------
731 | 
732 | 吴伟(@lazyparser)
733 | 
734 | - HelloGCC & HelloLLVM 社区负责人
735 | - 软件所PLCT实验室项目总监(Group Lead)
736 | - 本次课程的组织者和主要讲师
737 | 
738 | 
739 | 本次课程的内容
740 | -------------------
741 | 
742 | - 如何从零开始创建一个编译器项目
743 | - 一些非常细微的编程习惯
744 | - 一些非常细微的 git 使用习惯
745 | - 一些非常细微的测试和调试的思想
746 | 
747 | 以上内容不是按照所列次序讲解，而是一边敲代码一边介绍
748 | 
749 | 
750 | 第二课的课后练习（PL/0部分）
751 | +++++++++++++++++++++++++++++++
752 | 
753 | - 阅读PL/0的语言规范，尝试自己手写几个例子
754 | - 用之前小节提到的可视化工具尝试用RE实现词法分析的匹配部分
755 | - 从GitHub或者gitee上找一些参考的例子，看一看
756 | - 预习flex这个工具的语法及使用，跑个例子
757 | 
758 | 
759 | 重申：重在自学，本课程侧重网上没有的内容
760 | +++++++++++++++++++++++++++++++++++++++++++
761 | 
762 | - 包括USTC张昱老师的课程中也有公开PL/0的资料
763 | 
764 |   - http://staff.ustc.edu.cn/~yuzhang/compiler/2012s/lectures/basic_project.pdf
765 | 
766 | - 有不少学生或爱好者公开了自己的笔记和代码，可以借鉴
767 | 
768 |   - https://github.com/gdut-yy/PL0
769 |   - http://jcf94.com/download/2016-02-21-pl0-From_PL0_To_Flex.pdf
770 |   - https://github.com/IsaacZhu/PL0/blob/master/doc/
771 | 
772 |   在GitHub上搜PL0有大量不同版本的代码可以阅读和参考
773 | 
774 | 
775 | 词法、语法分析的实现方式之分
776 | +++++++++++++++++++++++++++++++
777 | 
778 | - 用 lex/yacc 或类似的生成器来构建
779 | 
780 |   - 可以快速构建原型系统或小语言；非常快速，熟练的一天就能出demo
781 |   - 工业级编程系统也有使用
782 |   - 主要问题是系统规模大了之后，改起来很头疼
783 | 
784 | - 手写的语法分析器，以及(或)手写的词法分析器
785 | 
786 |   - 很多工业级编译器都倾向于手写：清晰/速度
787 |   - 开发周期长一些；另外，你以为后续改动就容易驾驭了么
788 | 
789 | 
790 | 开始动手写点代码吧，先从哪里开始？
791 | ++++++++++++++++++++++++++++++++++++
792 | 
793 | - 原则：估计生存期超过24小时的代码，就应该用git管理起来
794 | - 习惯：git 的姓名和邮件设置要设置好，个人项目跟公司项目分开
795 | - 技巧：设置一些常用的 git 缩写，提高效率
796 | - 技巧：灵活运用 git 的 staged 和 unstaged 两种状态
797 | 
798 |   - https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository
799 | 
800 | - push 之前一定要检查：只要没 push，commits 都可以修改
801 | 
802 | 
803 | **（代码方面的具体操作过程，请参见本次课程的视频）**
804 | 
805 | 
806 | 一些编程能力之外的必知必会
807 | ++++++++++++++++++++++++++++
808 | 
809 | - 复制粘贴的时候要注意版权和开源许可证的兼容性
810 | 
811 |   - 这点我愿意多强调一些：国内目前关注的还太少
812 | 
813 | - 将工具生成的代码，跟你自己的改动，最好能够在 git 上区分开
814 | 
815 |   - 这样可以方便事后代码评审，并屏蔽掉工具升级带来的影响
816 |   - 如果不进行手工修改，不要跟踪工具生成的代码
817 | 
818 | - 能够自动化的过程，都应该自动化( 今天是 Makefile )
819 | 
820 | 
821 | 更快更强：如何高生产力的完成工作
822 | ++++++++++++++++++++++++++++++++++
823 | 
824 | - 在写代码的时候就要有所考虑：如何进行测试？
825 | 
826 |   - 打印一些log依然是主流和有用的调试方式
827 |   - 每一次打印的log都要有意义，是长期保存的代码/系统的一部分
828 |   - 避免使用「111、test、log」这样的输出信息，用更有信息的文本代替
829 | 
830 | - 如何避免调试(Debugging)？结构清晰、测试充分、定位容易
831 | - 如何高效率调试？后续课程再说
832 | 
833 | 
834 | 
835 | 
836 | 
837 | 
838 | 
839 | 
840 | 
841 | 
842 | 
843 | 
844 | 


--------------------------------------------------------------------------------
/doc/conf.py:
--------------------------------------------------------------------------------
  1 | # -*- coding: utf-8 -*-
  2 | #
  3 | # Configuration file for the Sphinx documentation builder.
  4 | #
  5 | # This file does only contain a selection of the most common options. For a
  6 | # full list see the documentation:
  7 | # http://www.sphinx-doc.org/en/stable/config
  8 | 
  9 | # -- Path setup --------------------------------------------------------------
 10 | 
 11 | # If extensions (or modules to document with autodoc) are in another directory,
 12 | # add these directories to sys.path here. If the directory is relative to the
 13 | # documentation root, use os.path.abspath to make it absolute, like shown here.
 14 | #
 15 | # import os
 16 | # import sys
 17 | # sys.path.insert(0, os.path.abspath('.'))
 18 | 
 19 | 
 20 | # -- Project information -----------------------------------------------------
 21 | 
 22 | project = u'bace'
 23 | copyright = u'2019, ZDZN'
 24 | author = u'ZDZN'
 25 | 
 26 | # The short X.Y version
 27 | version = u''
 28 | # The full version, including alpha/beta/rc tags
 29 | release = u'0.1.0'
 30 | 
 31 | 
 32 | # -- General configuration ---------------------------------------------------
 33 | 
 34 | # If your documentation needs a minimal Sphinx version, state it here.
 35 | #
 36 | # needs_sphinx = '1.0'
 37 | 
 38 | # Add any Sphinx extension module names here, as strings. They can be
 39 | # extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
 40 | # ones.
 41 | extensions = [
 42 | ]
 43 | 
 44 | # Add any paths that contain templates here, relative to this directory.
 45 | templates_path = ['_templates']
 46 | 
 47 | # The suffix(es) of source filenames.
 48 | # You can specify multiple suffix as a list of string:
 49 | #
 50 | # source_suffix = ['.rst', '.md']
 51 | source_suffix = '.rst'
 52 | 
 53 | # The master toctree document.
 54 | master_doc = 'bace lecture'
 55 | 
 56 | # The language for content autogenerated by Sphinx. Refer to documentation
 57 | # for a list of supported languages.
 58 | #
 59 | # This is also used if you do content translation via gettext catalogs.
 60 | # Usually you set "language" from the command line for these cases.
 61 | language = None
 62 | 
 63 | # List of patterns, relative to source directory, that match files and
 64 | # directories to ignore when looking for source files.
 65 | # This pattern also affects html_static_path and html_extra_path .
 66 | exclude_patterns = [u'_build', 'Thumbs.db', '.DS_Store']
 67 | 
 68 | # The name of the Pygments (syntax highlighting) style to use.
 69 | pygments_style = 'sphinx'
 70 | 
 71 | 
 72 | # -- Options for HTML output -------------------------------------------------
 73 | 
 74 | # The theme to use for HTML and HTML Help pages.  See the documentation for
 75 | # a list of builtin themes.
 76 | #
 77 | html_theme = 'alabaster'
 78 | 
 79 | # Theme options are theme-specific and customize the look and feel of a theme
 80 | # further.  For a list of options available for each theme, see the
 81 | # documentation.
 82 | #
 83 | # html_theme_options = {}
 84 | 
 85 | # Add any paths that contain custom static files (such as style sheets) here,
 86 | # relative to this directory. They are copied after the builtin static files,
 87 | # so a file named "default.css" will overwrite the builtin "default.css".
 88 | html_static_path = ['_static']
 89 | 
 90 | # Custom sidebar templates, must be a dictionary that maps document names
 91 | # to template names.
 92 | #
 93 | # The default sidebars (for documents that don't match any pattern) are
 94 | # defined by theme itself.  Builtin themes are using these templates by
 95 | # default: ``['localtoc.html', 'relations.html', 'sourcelink.html',
 96 | # 'searchbox.html']``.
 97 | #
 98 | # html_sidebars = {}
 99 | 
100 | 
101 | # -- Options for HTMLHelp output ---------------------------------------------
102 | 
103 | # Output file base name for HTML help builder.
104 | htmlhelp_basename = 'bacedoc'
105 | 
106 | 
107 | # -- Options for LaTeX output ------------------------------------------------
108 | latex_engine = 'xelatex'
109 | latex_elements = {
110 |     # The paper size ('letterpaper' or 'a4paper').
111 |     #
112 |     # 'papersize': 'letterpaper',
113 | 
114 |     # The font size ('10pt', '11pt' or '12pt').
115 |     #
116 |     # 'pointsize': '10pt',
117 | 
118 |     # Additional stuff for the LaTeX preamble.
119 |     #
120 |     # 'preamble': '',
121 | 
122 |     # Latex figure (float) alignment
123 |     #
124 |     # 'figure_align': 'htbp',
125 |     'fncychap' : '',
126 | 
127 |     'preamble': r'''\usepackage{ctex}
128 |     ''',
129 | }
130 | 
131 | # Grouping the document tree into LaTeX files. List of tuples
132 | # (source start file, target name, title,
133 | #  author, documentclass [howto, manual, or own class]).
134 | latex_documents = [
135 |     (master_doc, 'bace.tex', u'《方舟·编译技术入门与实战》 讲义',
136 |      u'ZDZN', 'manual'),
137 | ]
138 | 
139 | 
140 | # -- Options for manual page output ------------------------------------------
141 | 
142 | # One entry per manual page. List of tuples
143 | # (source start file, name, description, authors, manual section).
144 | man_pages = [
145 |     (master_doc, 'bace', u'《方舟·编译技术入门与实战》 讲义',
146 |      [author], 1)
147 | ]
148 | 
149 | 
150 | # -- Options for Texinfo output ----------------------------------------------
151 | 
152 | # Grouping the document tree into Texinfo files. List of tuples
153 | # (source start file, target name, title, author,
154 | #  dir menu entry, description, category)
155 | texinfo_documents = [
156 |     (master_doc, 'bace', u'《方舟·编译技术入门与实战》 讲义',
157 |      author, 'bace', 'One line description of project.',
158 |      'Miscellaneous'),
159 | ]
160 | 


--------------------------------------------------------------------------------
/doc/images/image01.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image01.png


--------------------------------------------------------------------------------
/doc/images/image02.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image02.png


--------------------------------------------------------------------------------
/doc/images/image03.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image03.png


--------------------------------------------------------------------------------
/doc/images/image04.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image04.png


--------------------------------------------------------------------------------
/doc/images/image05.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image05.png


--------------------------------------------------------------------------------
/doc/images/image06.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image06.png


--------------------------------------------------------------------------------
/doc/images/image07.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image07.png


--------------------------------------------------------------------------------
/doc/images/image08.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image08.png


--------------------------------------------------------------------------------
/doc/images/image09.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image09.png


--------------------------------------------------------------------------------
/doc/images/image10.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image10.png


--------------------------------------------------------------------------------
/doc/images/image11.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image11.png


--------------------------------------------------------------------------------
/doc/images/image12.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image12.png


--------------------------------------------------------------------------------
/doc/images/image13.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image13.png


--------------------------------------------------------------------------------
/doc/images/image14.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image14.png


--------------------------------------------------------------------------------
/doc/images/image15.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image15.png


--------------------------------------------------------------------------------
/doc/images/image16.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image16.png


--------------------------------------------------------------------------------
/doc/images/image17.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image17.png


--------------------------------------------------------------------------------
/doc/images/image18.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image18.png


--------------------------------------------------------------------------------
/doc/images/image19.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image19.png


--------------------------------------------------------------------------------
/doc/images/image20.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image20.png


--------------------------------------------------------------------------------
/doc/images/image21.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image21.png


--------------------------------------------------------------------------------
/doc/images/image22.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image22.png


--------------------------------------------------------------------------------
/doc/images/image23.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image23.png


--------------------------------------------------------------------------------
/doc/images/image24.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image24.png


--------------------------------------------------------------------------------
/doc/images/image25.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image25.png


--------------------------------------------------------------------------------
/doc/images/image26.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image26.png


--------------------------------------------------------------------------------
/doc/images/image27.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image27.png


--------------------------------------------------------------------------------
/doc/images/image28.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image28.png


--------------------------------------------------------------------------------
/doc/images/image29.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image29.png


--------------------------------------------------------------------------------
/doc/images/image30.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image30.png


--------------------------------------------------------------------------------
/doc/images/image31.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lazyparser/becoming-a-compiler-engineer/e623d47f0cedd0d4e8b807854ef82abb3e184bde/doc/images/image31.png


--------------------------------------------------------------------------------
/doc/index.rst:
--------------------------------------------------------------------------------
 1 | .. bace documentation master file, created by
 2 |    sphinx-quickstart on Tue Dec 10 21:05:58 2019.
 3 |    You can adapt this file completely to your liking, but it should at least
 4 |    contain the root `toctree` directive.
 5 | 
 6 | Welcome to bace's documentation!
 7 | ================================
 8 | 
 9 | .. toctree::
10 |    :hidden:
11 | 
12 |    bace lecture
13 | 
14 | :doc:`bace lecture`
15 | 


--------------------------------------------------------------------------------
/doc/make.bat:
--------------------------------------------------------------------------------
 1 | @ECHO OFF
 2 | 
 3 | pushd %~dp0
 4 | 
 5 | REM Command file for Sphinx documentation
 6 | 
 7 | if "%SPHINXBUILD%" == "" (
 8 | 	set SPHINXBUILD=sphinx-build
 9 | )
10 | set SOURCEDIR=.
11 | set BUILDDIR=_build
12 | set SPHINXPROJ=bace
13 | 
14 | if "%1" == "" goto help
15 | 
16 | %SPHINXBUILD% >NUL 2>NUL
17 | if errorlevel 9009 (
18 | 	echo.
19 | 	echo.The 'sphinx-build' command was not found. Make sure you have Sphinx
20 | 	echo.installed, then set the SPHINXBUILD environment variable to point
21 | 	echo.to the full path of the 'sphinx-build' executable. Alternatively you
22 | 	echo.may add the Sphinx directory to PATH.
23 | 	echo.
24 | 	echo.If you don't have Sphinx installed, grab it from
25 | 	echo.http://sphinx-doc.org/
26 | 	exit /b 1
27 | )
28 | 
29 | %SPHINXBUILD% -M %1 %SOURCEDIR% %BUILDDIR% %SPHINXOPTS%
30 | goto end
31 | 
32 | :help
33 | %SPHINXBUILD% -M help %SOURCEDIR% %BUILDDIR% %SPHINXOPTS%
34 | 
35 | :end
36 | popd
37 | 


--------------------------------------------------------------------------------