| /netbsd-src/external/apache2/llvm/dist/clang/docs/ |
| H A D | JSONCompilationDatabase.rst | 33 of compilation databases for Unix Makefile builds (Ninja builds in the
39 Clang's tooling interface supports reading compilation databases; see
47 A compilation database is a JSON file, which consist of an array of
67 - **directory:** The working directory of the compilation. All paths
71 compilation step. This is used by tools as the key into the
72 compilation database. There can be multiple command objects for the
76 this must be a valid command to rerun the exact compilation step for
83 - **output:** The name of the output created by this compilation step.
92 the build directory to detect the file and use the compilation database
|
| 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
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
[all …]
|
| /netbsd-src/external/gpl3/gcc.old/dist/contrib/reghunt/examples/ |
| H A D | 29906b.log | 7 Mon Feb 16 19:37:17 PST 2009 compilation failed for bug 29906b, id 1
22 Mon Feb 16 20:14:01 PST 2009 compilation failed for bug 29906b, id 70
27 Mon Feb 16 20:26:15 PST 2009 compilation failed for bug 29906b, id 104
37 Mon Feb 16 20:50:36 PST 2009 compilation failed for bug 29906b, id 112
42 Mon Feb 16 21:02:45 PST 2009 compilation failed for bug 29906b, id 116
47 Mon Feb 16 21:14:53 PST 2009 compilation failed for bug 29906b, id 118
52 Mon Feb 16 21:26:59 PST 2009 compilation failed for bug 29906b, id 119
57 Mon Feb 16 21:39:01 PST 2009 compilation failed for bug 29906b, id 120
|
| H A D | 29906a.log | 7 Mon Feb 16 18:14:43 PST 2009 compilation failed for bug 29906a, id 623
25 Mon Feb 16 18:33:05 PST 2009 compilation failed for bug 29906a, id 467
31 Mon Feb 16 18:39:07 PST 2009 compilation failed for bug 29906a, id 389
73 Mon Feb 16 19:20:56 PST 2009 compilation failed for bug 29906a, id 388
|
| /netbsd-src/external/gpl3/gcc/dist/contrib/reghunt/examples/ |
| H A D | 29906b.log | 7 Mon Feb 16 19:37:17 PST 2009 compilation failed for bug 29906b, id 1
22 Mon Feb 16 20:14:01 PST 2009 compilation failed for bug 29906b, id 70
27 Mon Feb 16 20:26:15 PST 2009 compilation failed for bug 29906b, id 104
37 Mon Feb 16 20:50:36 PST 2009 compilation failed for bug 29906b, id 112
42 Mon Feb 16 21:02:45 PST 2009 compilation failed for bug 29906b, id 116
47 Mon Feb 16 21:14:53 PST 2009 compilation failed for bug 29906b, id 118
52 Mon Feb 16 21:26:59 PST 2009 compilation failed for bug 29906b, id 119
57 Mon Feb 16 21:39:01 PST 2009 compilation failed for bug 29906b, id 120
|
| H A D | 29906a.log | 7 Mon Feb 16 18:14:43 PST 2009 compilation failed for bug 29906a, id 623
25 Mon Feb 16 18:33:05 PST 2009 compilation failed for bug 29906a, id 467
31 Mon Feb 16 18:39:07 PST 2009 compilation failed for bug 29906a, id 389
73 Mon Feb 16 19:20:56 PST 2009 compilation failed for bug 29906a, id 388
|
| /netbsd-src/external/apache2/llvm/dist/clang/tools/scan-build-py/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]
|
| /netbsd-src/external/gpl3/gcc/dist/gcc/jit/docs/cp/topics/ |
| H A D | compilation.rst | 28 compilation), although any errors that occur on the context will
29 prevent any future compilation of that context.
31 In-memory compilation
43 Ahead-of-time compilation
46 Although libgccjit is primarily aimed at just-in-time compilation, it
|
| /netbsd-src/external/gpl3/gcc.old/dist/gcc/jit/docs/cp/topics/ |
| H A D | compilation.rst | 28 compilation), although any errors that occur on the context will
29 prevent any future compilation of that context.
31 In-memory compilation
43 Ahead-of-time compilation
46 Although libgccjit is primarily aimed at just-in-time compilation, it
|
| /netbsd-src/external/apache2/llvm/dist/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
|
| /netbsd-src/external/apache2/llvm/dist/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
|
| /netbsd-src/external/apache2/llvm/dist/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
|
| /netbsd-src/external/apache2/llvm/dist/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`).
70 re-enter the ORC (e.g. to request lazy compilation) concurrently from multiple
92 compilation of LLVM IR and linking of relocatable object files. All operations
99 compilation of LLVM IR. When an LLVM IR module is added via the addLazyIRModule
137 // Build an LLLazyJIT instance that uses four worker threads for compilation,
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.
[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*,
258 clang uses *merged parsing*. This is similar to split compilation, except all
260 compilation steps.
280 ``F`` is passed to this compilation, and clang includes it in a special ELF
[all …]
|
| /netbsd-src/external/gpl3/gcc.old/dist/gcc/doc/ |
| H A D | lto.texi | 16 so that all the different compilation units that make up
53 doubling compilation time and increasing file sizes up to 5x the
66 When @option{-flto} is given during compilation of a source file, the
94 effective compilation of large programs. For this reason GCC implements two
95 link-time compilation modes.
100 were a single source-level compilation unit.
103 CPUs and/or a distributed compilation environment to quickly link
107 files and distributes the compilation of the sub-graphs to different
110 Note that distributed compilation is not implemented yet, but since
121 the LTO and WHOPR compilation mode.
[all …]
|
| /netbsd-src/external/bsd/am-utils/dist/m4/macros/ |
| H A D | opt_amu_cflags.m4 | 2 dnl Which options to add to CFLAGS for compilation?
5 [AC_MSG_CHECKING(for additional C option compilation flags)
|
| /netbsd-src/external/bsd/file/dist/magic/magdir/ |
| H A D | rust | 15 # Rust incremental compilation metadata
19 >4 uleshort =0 Rust incremental compilation metadata
|
| /netbsd-src/external/gpl3/gcc/dist/gcc/doc/ |
| H A D | lto.texi | 16 so that all the different compilation units that make up
65 When @option{-flto} is given during compilation of a source file, the
93 effective compilation of large programs. For this reason GCC implements two
94 link-time compilation modes.
99 were a single source-level compilation unit.
102 CPUs and/or a distributed compilation environment to quickly link
106 files and distributes the compilation of the sub-graphs to different
109 Note that distributed compilation is not implemented yet, but since
120 the LTO and WHOPR compilation mode.
139 compilation. In LTO, WPA and LTRANS are executed within a single
[all …]
|
| /netbsd-src/external/apache2/llvm/dist/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
|
| /netbsd-src/external/gpl3/gcc.old/dist/gcc/jit/docs/topics/ |
| H A D | compilation.rst | 28 compilation), although any errors that occur on the context will
29 prevent any future compilation of that context.
31 In-memory compilation
141 Ahead-of-time compilation
144 Although libgccjit is primarily aimed at just-in-time compilation, it
|
| /netbsd-src/external/gpl3/gcc/dist/gcc/jit/docs/topics/ |
| H A D | compilation.rst | 28 compilation), although any errors that occur on the context will
29 prevent any future compilation of that context.
31 In-memory compilation
141 Ahead-of-time compilation
144 Although libgccjit is primarily aimed at just-in-time compilation, it
|
| /netbsd-src/external/bsd/wpa/dist/wpa_supplicant/wpa_gui-qt4/ |
| H A D | wpa_gui.pro | 15 # cross compilation to win32
21 # cross compilation to win32
|
| /netbsd-src/external/mit/expat/dist/ |
| H A D | Changes | 88 compilation with CMake from installed sources
139 #529 #539 CI: Cover compilation with -m32
222 #332 #470 For (non-default) compilation with -DEXPAT_MIN_SIZE=ON (CMake)
325 to fix compilation with CMake from installed sources
345 #385 CMake: Fix compilation with -DEXPAT_SHARED_LIBS=OFF for
347 CMake: Expose man page compilation as target "xmlwf-manpage"
464 #330 CMake: Fix compilation for 16bit character types,
511 #247 #248 Autotools: Fix compilation for lack of docbook2x-man
558 #180 Windows: Fix compilation of test suite for Visual Studio 2008
597 #127 Windows: Fix test suite compilation
[all …]
|
| /netbsd-src/external/mit/libcbor/dist/doc/source/ |
| H A D | getting_started.rst | 89 libcbor is known to successfully work on ARM Android devices. Cross-compilation is possible with ``…
176 …FIX`` (if you provided it) was correct. Including the path path during compilation should suffice,…
190 …Verify the linkage using ``ldd``, ``otool``, or similar and adjust the compilation directives acco…
200 **compilation failed**: If your compiler supports C99 yet the compilation has failed, please report…
|