| /llvm-project-15.0.7/clang/test/Driver/ |
| H A D | cuda-bail-out.cu | 7 #error compilation failed
20 #error compilation failed
24 #error compilation failed
28 #error compilation failed
|
| H A D | hip-output-file-name.hip | 4 // Output bundled code objects for combined compilation.
20 // Output unbundled PPE for one GPU for device only compilation.
25 // Output bundled PPE for two GPUs for mixed compilation.
30 // Output bundled PPE for two GPUs for mixed compilation with -save-temps.
35 // Output unbundled PPE for two GPUs for device only compilation.
40 // Output bundled PPE for two GPUs for device only compilation with --gpu-bundle-output.
50 // Output unbundled PPE for host only compilation.
62 // Output bundled PPE for two GPUs for mixed compilation.
67 // Output bundled PPE for two GPUs for mixed compilation.
72 // Output bundled PPE for two GPUs for device only compilation with --gpu-bundle-output.
[all …]
|
| H A D | hip-inputs.hip | 21 // CHECK-NOT: error: mixed CUDA and HIP compilation is not supported
22 // MIX: error: mixed CUDA and HIP compilation is not supported
|
| H A D | hip-phases.hip | 4 // - Host/device-only compilation;
162 // compilation mode.
176 // compilation mode.
189 // compilation mode.
204 // compilation mode.
217 // compilation mode.
234 // compilation mode.
249 // compilation mode.
273 // compilation mode.
362 // compilation mode. bundle.
[all …]
|
| /llvm-project-15.0.7/clang/test/Index/ |
| H A D | compile_commands.json | 18 # RUN: c-index-test -compilation-db %s
19 # RUN: c-index-test -compilation-db lookup file_does_not_exists.cpp %s | FileCheck -check-prefix=FI…
20 # FILE-NOT-FOUND: file file_does_not_exists.cpp not found in compilation db
22 # RUN: c-index-test -compilation-db lookup /home/john.doe/MyProject/project.cpp %s | FileCheck -che…
25 # RUN: c-index-test -compilation-db lookup /home/john.doe/MyProject/project2.cpp %s | FileCheck -ch…
|
| /llvm-project-15.0.7/clang/docs/ |
| H A D | JSONCompilationDatabase.rst | 32 Clang has the ablity to generate compilation database fragments via
34 fragments together between ``[`` and ``]`` to create a compilation database.
37 of compilation databases for Unix Makefile builds (Ninja builds in the
43 `Bazel <https://bazel.build>`_ can export a compilation database via
49 Clang's tooling interface supports reading compilation databases; see
57 A compilation database is a JSON file, which consist of an array of
82 - **directory:** The working directory of the compilation. All paths
86 compilation step. This is used by tools as the key into the
87 compilation database. There can be multiple command objects for the
101 - **output:** The name of the output created by this compilation step.
[all …]
|
| H A D | DriverInternals.rst | 56 work compared to a compilation, but we have tried to keep it as
161 the desired compilation sequence are constructed. This involves
192 A rather different compilation pipeline is shown here; in this
240 compilation for a particular architecture, platform, and operating
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
305 compilation sequence. For example, the list of used temporary files
307 (which should be removed if compilation fails).
354 When a compilation is successful (there are no errors), the driver
[all …]
|
| /llvm-project-15.0.7/clang/tools/scan-build-py/lib/libscanbuild/ |
| H A D | intercept.py | 34 from libscanbuild.compilation import split_command
213 compilation = split_command(exec_trace['command'])
214 if compilation:
215 for source in compilation.files:
216 compiler = 'c++' if compilation.compiler == 'c++' else 'cc'
217 command = [compiler, '-c'] + compilation.flags + [source]
|
| /llvm-project-15.0.7/llvm/cmake/platforms/ |
| H A D | ClangClCMakeCompileRules.cmake | 3 # input file path to force it to be treated as a path. CMake's compilation rules
5 # CMake versions, overriding compilation rules works well enough. This file will
6 # be included by cmake after the default compilation rules have already been set
|
| /llvm-project-15.0.7/clang/tools/scan-build-py/ |
| H A D | README.md | 5 intercepted and logged into a [compilation database][1] and/or piped to
32 To generate a compilation database file goes like this:
36 To run the Clang static analyzer against a project with compilation database
47 To run the CTU analysis, a compilation database file has to be created:
51 To run the Clang Static Analyzer against a compilation database
103 The 1. runs the analyzer right after the real compilation. So, if the build
107 The 2. and 3. generate the compilation database first, and filters out those
116 compilation database. `analyze-build` does only run the analyzer against the
|
| /llvm-project-15.0.7/llvm/test/tools/dsymutil/ |
| H A D | basic-linking.test | 10 CHECK: Input compilation unit:
16 CHECK: Input compilation unit:
22 CHECK: Input compilation unit:
72 CHECK-LTO: Input compilation unit:
76 CHECK-LTO: Input compilation unit:
80 CHECK-LTO: Input compilation unit:
119 CHECK-ARCHIVE: Input compilation unit:
125 CHECK-ARCHIVE: Input compilation unit:
131 CHECK-ARCHIVE: Input compilation unit:
|
| /llvm-project-15.0.7/llvm/test/tools/llvm-profgen/ |
| H A D | split-dwarf.test | 35 ; split-dwarf-single.o: clang -gsplit-dwarf=single -fdebug-compilation-dir=. test.c -fdebu…
36 ; split-dwarf-single.exe: clang -fdebug-compilation-dir=. split-dwarf-single.o -o split-dwarf-…
38 ; split-dwarf-split.dwo: clang -gsplit-dwarf=split -fdebug-compilation-dir=. test.c -fdebug-…
39 ; split-dwarf-split.exe: clang -fdebug-compilation-dir=. split-dwarf-split.o -o split-dwarf-s…
|
| /llvm-project-15.0.7/llvm/docs/HistoricalNotes/ |
| H A D | 2001-04-16-DynamicCompilation.txt | 6 between these two complementary stages of compilation. We feel that
12 compiler may fall in anywhere in a "continuum of compilation" to do its
22 From a technical perspective, pure static compilation cannot ever give
30 On a social level, static compilation is a very shortsighted solution to
|
| H A D | 2001-06-20-.NET-Differences.txt | 9 indicated that the goal seems to be to do simple static compilation (very
11 "relies on dynamic class loading and JIT compilation".
|
| /llvm-project-15.0.7/libcxx/src/include/ryu/ |
| H A D | ryu.h | 110 } else if (_Precision < 1'000'000'000) { // Match ' to fix compilation with GCC in C++11 mode in _Floating_to_chars_scientific_precision()
131 } else if (_Precision < 1'000'000'000) { // Match ' to fix compilation with GCC in C++11 mode in _Floating_to_chars_fixed_precision()
|
| /llvm-project-15.0.7/clang/test/ClangScanDeps/ |
| H A D | subframework_header_dir_symlink.m | 11 // RUN: clang-scan-deps -compilation-database %t.cdb -j 1 -reuse-filemanager=0 | \
13 // RUN: clang-scan-deps -compilation-database %t.cdb -j 1 -reuse-filemanager=1 | \
|
| /llvm-project-15.0.7/llvm/test/tools/llvm-dwarfdump/X86/ |
| H A D | debug-names-verify-cu-lists.s | 62 .long 0 # Header: compilation unit count
79 .long 2 # Header: compilation unit count
98 .long 1 # Header: compilation unit count
|
| H A D | debug-names-find.s | 101 .long 1 # Header: compilation unit count
145 # Index of compilation unit 1. This one has no hash table.
150 .long 1 # Header: compilation unit count
|
| H A D | debug-names-misaligned.s | 25 .long 1 # Header: compilation unit count
57 .long 1 # Header: compilation unit count
|
| /llvm-project-15.0.7/llvm/docs/tutorial/ |
| H A D | BuildingAJIT3.rst | 33 may also do a lot of unnecessary compilation if only a few compiled functions
35 defer the compilation of any given function until the moment that function is
55 will trigger compilation and then execution of a function. By initializing the
57 compilation: The first attempted call to the function will follow the function
66 lazy compilation. We just need a few changes to the source:
138 request compilation of the function that was called. Next we pass a reference to
177 layer added to enable lazy function-at-a-time compilation. To build this example, use:
|
| H A D | BuildingAJIT1.rst | 22 introduces new features like concurrent compilation, optimization, lazy
23 compilation and remote execution.
85 support for concurrent compilation, optimization and lazy compilation.
170 a compiler instance to use to perform the actual compilation from IR to object
236 in the JITDylib for each definition in the module, and will defer compilation of
238 compilation: just referencing a definition, even if it is never used, will be
239 enough to trigger compilation. In later chapters we will teach our JIT to defer
240 compilation of functions until they're actually called. To add our Module we
244 duration of the JIT. Once we switch to concurrent compilation in later chapters
249 As noted above, lookup will implicitly trigger compilation for any symbol
|
| /llvm-project-15.0.7/llvm/docs/ |
| H A D | ORCv2.rst | 26 evaluation. In this use case, cross compilation allows expressions compiled
50 **LLVM IR compilation**
54 **Eager and lazy compilation**
59 compilation via lazy-reexports (see :ref:`Laziness`).
92 compilation of LLVM IR and linking of relocatable object files. All operations
142 // JIT'd code will jump here if lazy compilation fails, giving us an
211 This example tells us nothing about *how* or *when* compilation will happen.
434 compilation, concurrent JIT'd code, and speculative compilation.
949 ORC's support for concurrent compilation allows us to easily enable
950 *speculative* JIT compilation: compilation of code that is not needed yet,
[all …]
|
| H A D | CompileCudaWithLLVM.rst | 39 CUDA compilation is supported on Linux. Compilation on MacOS and Windows may or
45 Invoking clang for CUDA compilation works similarly to compiling regular C++.
78 v10.0 CUDA SDK `no longer supports compilation of 32-bit
199 This is tricky, because NVCC may invoke clang as part of its own compilation
207 compilation, in host and device modes:
219 Both clang and nvcc define ``__CUDACC__`` during CUDA compilation. You can
235 compilation models used by clang and nvcc. nvcc uses *split compilation*,
260 compilation steps.
288 host compilation and during device compilation for each GPU architecture.)
448 // clang generates an error here, because during host compilation, we
[all …]
|
| /llvm-project-15.0.7/mlir/utils/mbr/ |
| H A D | README.md | 2 MBR is a tool to run benchmarks. It measures compilation and running times of
11 As mentioned in the intro, this tool measures compilation and running times.
45 The `compiler` callable is optional if there is no compilation step, for
|
| /llvm-project-15.0.7/mlir/docs/Tools/ |
| H A D | MLIRLSP.md | 138 server relies on a compilation database to provide build-system information for
145 A PDLL compilation database is a YAML file, conventionally named
162 Per convention, PDLL compilation databases should be named
164 using CMake and `mlir_pdll`, a compilation database is generally automatically
234 stages of compilation, such as the AST, the `.mlir` containing the generated
263 server relies on a compilation database to provide build-system information for
270 A TableGen compilation database is a YAML file, conventionally named
287 Per convention, TableGen compilation databases should be named
289 When using CMake and `mlir_tablegen`, a compilation database is generally
433 [`pdll_compile_commands.yml` files](https://mlir.llvm.org/docs/Tools/MLIRLSP/#compilation-database)
[all …]
|