| /llvm-project-15.0.7/clang/test/Driver/ |
| H A D | check-time-trace-sections.py | 18 backends = [event for event in events if event["name"] == "Backend"] variable
33 for backend in backends]):
|
| /llvm-project-15.0.7/llvm/bindings/ocaml/ |
| H A D | CMakeLists.txt | 4 add_subdirectory(backends)
|
| /llvm-project-15.0.7/llvm/bindings/ocaml/all_backends/ |
| H A D | llvm_all_backends.mli | 9 (** Initialize all the backends targets *)
|
| /llvm-project-15.0.7/llvm/docs/TableGen/ |
| H A D | index.rst | 58 To be useful, one of the `backends`_ must be used. These backends are
263 TableGen backends
283 backends, and see the :doc:`TableGen Backend Developer's Guide <./BackGuide>`
296 the basic concepts via custom-made backends, which can pervert the original
301 backends adhere to strict rules. Others are suggesting we should move to less,
|
| H A D | BackGuide.rst | 18 to various backends, which extract information from a subset of the records
24 provided by TableGen for the backends. For a complete reference to the
30 TableGen source files. For a description of the existing backends, see
480 * The list of includes is the minimal list required by most backends.
680 difficult for backends to report clear error messages with accurate source
719 TableGen provides some tools to aid in debugging backends.
|
| H A D | BackEnds.rst | 11 TableGen backends are at the core of TableGen's functionality. The source
20 features. Some backends generate output that is consumed by more than one
22 preprocessor tricks to be used. Some backends can also print C++ code
470 for writing custom backends without having to modify TableGen itself,
579 These values are not expected to be needed by backends. The standard
|
| H A D | ProgRef.rst | 18 to various *backends*, which extract information from a subset of the records
33 for a description of the LLVM TableGen backends, and :doc:`TableGen
37 Here are a few of the things backends can do.
67 backends will process. Note that TableGen assigns no meanings to fields; the
68 meanings are entirely up to the backends and the programs that incorporate
69 the output of those backends.
1301 backends. Here is an example of an ``assert`` in two class definitions.
|
| /llvm-project-15.0.7/lld/ |
| H A D | CODE_OWNERS.TXT | 14 D: COFF, ELF backends (COFF/* ELF/*)
|
| /llvm-project-15.0.7/llvm/test/tools/gold/X86/ |
| H A D | thinlto_emit_imports.ll | 8 ; Ensure gold generates imports files if requested for distributed backends.
|
| /llvm-project-15.0.7/clang/docs/ |
| H A D | ThinLTO.rst | 26 later when the modules are optimized in fully parallel backends.
28 the ThinLTO backends in threads. So the usage model is not affected
29 as the distinction between the fast serial thin link step and the backends
|
| /llvm-project-15.0.7/llvm/bindings/ocaml/llvm/ |
| H A D | META.llvm.in | 115 description = "All backends for LLVM"
|
| /llvm-project-15.0.7/lld/test/COFF/ |
| H A D | thinlto-emit-imports.ll | 11 ; Ensure lld generates imports files if requested for distributed backends.
|
| /llvm-project-15.0.7/llvm/docs/CommandGuide/ |
| H A D | bugpoint.rst | 143 respectively. The interpreter and the JIT backends cannot currently
144 be used as the "safe" backends.
|
| /llvm-project-15.0.7/llvm/test/CodeGen/AMDGPU/GlobalISel/ |
| H A D | no-cse-nonlocal-convergent-instrs.mir | 12 # actual bug in the AMDGPU backend. The current open source GPU backends as is
|
| /llvm-project-15.0.7/lld/test/ELF/lto/ |
| H A D | thinlto-emit-imports.ll | 11 ; Ensure lld generates imports files if requested for distributed backends.
|
| /llvm-project-15.0.7/llvm/docs/ |
| H A D | UserGuides.rst | 179 Information on how to write LLVM backends for machine targets.
|
| H A D | BranchWeightMetadata.rst | 222 and we need to ensure the IR matches in the ThinLTO backends for profile
|
| H A D | HowToBuildWithPGO.rst | 62 - some coverage of other architectures (if other arches are supported backends).
|
| H A D | NewPassManager.rst | 154 Sometimes either frontends or backends will want to inject passes into the
156 backends may want to add passes that lower custom intrinsics. For these
|
| H A D | FuzzingLLVM.rst | 222 The ``FuzzMutate`` library is used to structurally fuzz backends in
|
| H A D | OpaquePointers.rst | 91 regards to address spaces. People maintaining backends that care a lot about
|
| /llvm-project-15.0.7/openmp/docs/ |
| H A D | SupportAndFAQ.rst | 57 <https://llvm.org/docs/GettingStarted.html>`__.). Make sure all backends that
59 backends enabled. When building with `LLVM_ENABLE_RUNTIMES="openmp"` OpenMP
|
| /llvm-project-15.0.7/polly/docs/ |
| H A D | UsingPollyWithClang.rst | 49 The OpenMP backends can be further influenced using the following CL switches:
|
| /llvm-project-15.0.7/llvm/test/ThinLTO/X86/ |
| H A D | devirt2.ll | 73 ; Index based WPD, distributed backends
|
| /llvm-project-15.0.7/llvm/include/llvm/Target/ |
| H A D | TargetInstrPredicate.td | 54 // Tablegen backends know how to expand MCInstPredicate definitions into actual
|