Searched refs:compilations (Results 1 – 19 of 19) sorted by relevance
172 CompilationDatabase &compilations) { in HandleFiles() argument189 ClangTool Tool(compilations, SourcesToBeParsed); in HandleFiles()
6 // Check that there are commands for both host- and device-side compilations.
11 # before all lib compilations via the clang-tablegen-targets target; the
34 many compilations but it is not 100% complete. Users seeking to compile
8 // Basic check on one of the compilations.
6 compilations independently of the build system.
17 The tool chain may perform multiple compilations of a translation unit to
37 in some compilations:
801 In a simpler word, we could get rid of many redundant compilations by using modules.872 …her optimization levels the definitions of such functions are provided to user compilations for the
85 Adds most of builtin types and function declarations during compilations. By
57 build when all compilations require the PCH file to be up-to-date.
3005 across split compilations, mainly to support SYCL/Data Parallel C++ language.
760 compilations steps.
492 // post-regalloc) path for -O0 compilations. Fortunately this path can be
435 # file used by our object library compilations.
2609 HelpText<"Compile CUDA code for host only. Has no effect on non-CUDA compilations.">;2612 "effect on non-CUDA compilations.">;
6449 // post-regalloc) path for -O0 compilations. Fortunately this path can be
7454 Offloading compilations need to embed device code into the host section table to