Lines Matching full:compilation
56 work compared to a compilation, but we have tried to keep it as
158 #. **Pipeline: Compilation Job Construction**
161 the desired compilation sequence are constructed. This involves
192 A rather different compilation pipeline is shown here; in this
215 After this stage is complete the compilation process is divided into
218 there is no "real" final output). Phases are well known compilation
240 compilation for a particular architecture, platform, and operating
242 during one compilation in order to interact with tools for separate
261 bound for this compilation sequence. Here clang is being used to
270 compilation. The main work is in translating from the gcc style
288 Finally, the compilation pipeline is executed. This is mostly
295 The Compilation Object
298 The driver constructs a Compilation object for each set of command line
300 construction of a Compilation; an IDE should be able to construct a
304 The Compilation object holds information that is particular to each
305 compilation sequence. For example, the list of used temporary files
306 (which must be removed once compilation is finished) and result files
307 (which should be removed if compilation fails).
312 Parsing and pipelining both occur without reference to a Compilation
350 argument of whether it has been used (at all) during the compilation.
354 When a compilation is successful (there are no errors), the driver
374 to alter the compilation itself (for example, one cannot provide
388 control the compilation pipeline are generally part of the *Pipeline*
398 compilation environments. All platform and tool chain specific code
