@@ -166,11 +166,12 @@ LLVM version: 4.0
166
166
There are two workflows that are useful for faster builders of the
167
167
compiler.
168
168
169
- ** Check, check, and check again.** The first workflow, which is useful when doing
170
- simple refactorings, is to run ` ./x.py check ` continuously. Here you
171
- are just checking that the compiler can ** build** , but often that is
172
- all you need (e.g., when renaming a method). You can then run ` ./x.py build `
173
- when you acqtually need to run tests.
169
+ ** Check, check, and check again.** The first workflow, which is useful
170
+ when doing simple refactorings, is to run ` ./x.py check `
171
+ continuously. Here you are just checking that the compiler can
172
+ ** build** , but often that is all you need (e.g., when renaming a
173
+ method). You can then run ` ./x.py build ` when you acqtually need to
174
+ run tests.
174
175
175
176
In fact, it is eomtimes useful to put off tests even when you are not
176
177
100% sure the code will work. You can then keep building up
@@ -192,7 +193,8 @@ don't work (but that is easily detected and fixed).
192
193
The sequence of commands you want is as follows:
193
194
194
195
- Initial build: ` ./x.py build -i --stage 1 src/libstd `
195
- - As [ documented above] ( #command ) , this will build a functional stage1 compiler
196
+ - As [ documented above] ( #command ) , this will build a functional
197
+ stage1 compiler
196
198
- Subsequent builds: ` ./x.py build -i --stage 1 src/libstd --keep-stage 1 `
197
199
- Note that we added the ` --keep-stage 1 ` flag here
198
200
0 commit comments