Phases of translation
Phases of translation
The C++ source file is processed by the compiler as if the following phases take place, in this exact order:
Phase 1
'0'
to '9'
'a'
to 'z'
and from 'A'
to 'Z'
_ { } [ ] # ( ) < > % : ; . ? * + - / ^ & | ~ ! = , \ " '
\u
or \U
) or by some implementation-defined form that is handled equivalently.3) Trigraph sequences are replaced by corresponding single-character representations. | (until C++17) |
Phase 2
\uXXX
) is formed in this phase, the behavior is undefined.Phase 3
2) Any transformations performed during phases 1 and 2 between the initial and the final double quote of any raw string literal are reverted. | (since C++11) |
Newlines are kept, and it's unspecified whether non-newline whitespace sequences may be collapsed into single space characters.
Phase 4
Phase 5
Note: the conversion performed at this stage can be controlled by command line options in some implementations: gcc and clang use -finput-charset
to specify the encoding of the source character set, -fexec-charset
and -fwide-exec-charset
to specify the encodings of the execution character set in the string and character literals that don't have an encoding prefix (since C++11).
Phase 6
Adjacent string literals are concatenated.
Phase 7
Compilation takes place: each preprocessing token is converted to a token. The tokens are syntactically and semantically analyzed and translated as a translation unit.
Phase 8
Each translation unit is examined to produce a list of required template instantiations, including the ones requested by explicit instantiations. The definitions of the templates are located, and the required instantiations are performed to produce instantiation units.
Phase 9
Translation units, instantiation units, and library components needed to satisfy external references are collected into a program image which contains information needed for execution in its execution environment.
Notes
Some compilers don't implement instantiation units (also known as template repositories or template registries) and simply compile each template instantiation at Phase 7, storing the code in the object file where it is implicitly or explicitly requested, and then the linker collapses these compiled instantiations into one at Phase 9.
References
- C++11 standard (ISO/IEC 14882:2011):
- 2.2 Phases of translation [lex.phases]
- C++98 standard (ISO/IEC 14882:1998):
- 2.1 Phases of translation [lex.phases]
See also
C documentation for phases of translation |
© cppreference.com
Licensed under the Creative Commons Attribution-ShareAlike Unported License v3.0.
http://en.cppreference.com/w/cpp/language/translation_phases