forked from OSchip/llvm-project
Documentation: PTHInternals: use correct adornments and fix typos
Fixes PR14014 llvm-svn: 171005
This commit is contained in:
parent
46735cb9ce
commit
114d895e26
|
@ -60,7 +60,7 @@ lexing and preprocessing of a source file, while parsing and
|
||||||
type-checking must be completely redone every time a PTH file is used.
|
type-checking must be completely redone every time a PTH file is used.
|
||||||
|
|
||||||
Basic Design Tradeoffs
|
Basic Design Tradeoffs
|
||||||
~~~~~~~~~~~~~~~~~~~~~~
|
----------------------
|
||||||
|
|
||||||
In the long term there are plans to provide an alternate PCH
|
In the long term there are plans to provide an alternate PCH
|
||||||
implementation for Clang that also caches the work for parsing and type
|
implementation for Clang that also caches the work for parsing and type
|
||||||
|
@ -89,7 +89,7 @@ features:
|
||||||
**Architecture independence**
|
**Architecture independence**
|
||||||
In contrast to GCC's PCH files (and
|
In contrast to GCC's PCH files (and
|
||||||
those of several other compilers), Clang's PTH files are architecture
|
those of several other compilers), Clang's PTH files are architecture
|
||||||
independent, requiring only a single PTH file when building an
|
independent, requiring only a single PTH file when building a
|
||||||
program for multiple architectures.
|
program for multiple architectures.
|
||||||
|
|
||||||
For example, on Mac OS X one may wish to compile a "universal binary"
|
For example, on Mac OS X one may wish to compile a "universal binary"
|
||||||
|
@ -142,7 +142,7 @@ advantages just mentioned but would also retain some of the strengths of
|
||||||
PTH such as reduced memory pressure (ideal for multi-core builds).
|
PTH such as reduced memory pressure (ideal for multi-core builds).
|
||||||
|
|
||||||
Internal PTH Optimizations
|
Internal PTH Optimizations
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
--------------------------
|
||||||
|
|
||||||
While the main optimization employed by PTH is to reduce lexing time of
|
While the main optimization employed by PTH is to reduce lexing time of
|
||||||
header files by caching pre-lexed tokens, PTH also employs several other
|
header files by caching pre-lexed tokens, PTH also employs several other
|
||||||
|
@ -154,7 +154,7 @@ optimizations to speed up the processing of header files:
|
||||||
involved in context-switching to the kernel to resolve included
|
involved in context-switching to the kernel to resolve included
|
||||||
files.
|
files.
|
||||||
|
|
||||||
- Fasting skipping of ``#ifdef``... ``#endif`` chains: PTH files
|
- Fast skipping of ``#ifdef`` ... ``#endif`` chains: PTH files
|
||||||
record the basic structure of nested preprocessor blocks. When the
|
record the basic structure of nested preprocessor blocks. When the
|
||||||
condition of the preprocessor block is false, all of its tokens are
|
condition of the preprocessor block is false, all of its tokens are
|
||||||
immediately skipped instead of requiring them to be handled by
|
immediately skipped instead of requiring them to be handled by
|
||||||
|
|
Loading…
Reference in New Issue