Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched full:backend (Results 1251 - 1275 of 2151) sorted by null

<<51525354555657585960>>

/external/selinux/libselinux/src/
label_file.c	2 * File contexts backend for labeling system 641 selinux_log(SELINUX_ERROR, "No path given to file labeling backend\n"); 685 * Backend interface routines
/external/swiftshader/third_party/LLVM/docs/
HowToSubmitABug.html	228 which code generator you wish to compile the program with (e.g. C backend, the 257 Backend, and then link in the shared object it generates.</p> 293 backend and the <em>test</em> file which either LLC or the JIT
ReleaseNotes.html	440 LLVM code generation backend in Mini, the JIT compiler.</p> 467 symbolic fashion. The interpreter uses LLVM as a backend to JIT-compile Pure 493 machine code is then generated from this bitcode by an LLVM backend on the 540 loads them in to the compiler backend as runtime libraries to avoid     [all...]
CodeGenerator.html	109 <li><a href="#x86">The X86 backend</a></li> 110 <li><a href="#ppc">The PowerPC backend</a> 117 <li><a href="#ptx">The PTX backend</a></li> 184 want to add a backend for a new target, you will need 204 required to be defined for a backend to fit into the LLVM system, but the 210 C backend does not require register allocation, instruction selection, or any 213 a code generator like this is a (purely hypothetical) backend that converts 545 specific backend. All of the instructions for a target should be defined in     [all...]
/toolchain/binutils/binutils-2.25/bfd/
libaout.h	100 /* a.out backend linker hash table entries. */ 111 /* a.out backend linker hash table. */ 458 used by the a.out backend linker. */
coff-mips.c	348 this backend routine. It must fill in the howto field. */     [all...]
ChangeLog-9495	[all...]
coff-alpha.c	461 /* This is a hook called by coff_real_object_p to create any backend 596 this backend routine. It must fill in the howto field. */     [all...]
/external/llvm/docs/
CodeGenerator.rst	71 classes. If you want to add a backend for a new target, you will need to 86 backend to fit into the LLVM system, but the others must be defined if the 90 completely non-traditional code generation targets. For example, the C backend 93 two interfaces, and does its own thing. Note that C backend was removed from the 95 (purely hypothetical) backend that converts LLVM to the GCC RTL form and uses 346 specific backend. All of the instructions for a target should be defined in the     [all...]
WritingAnLLVMBackend.rst	2 Writing an LLVM Backend 21 The backend of LLVM features a target-independent code generator that may 23 ARM, and SPARC. The backend may also be used to generate code targeted at SPUs 36 The audience for this document is anyone who needs to write an LLVM backend to 75 To write a compiler backend for LLVM that converts the LLVM IR to code for a 129 To actually create your compiler backend, you need to create and modify a few     [all...]
Atomics.rst	170 which writes to surrounding bytes. (If you are writing a backend for an 416 One very important property of the atomic operations is that if your backend 465 For an example of all of these, look at the ARM backend.
GetElementPtr.rst	296 I'm writing a backend for a target which needs custom lowering for GEP. How do I do this? 300 Typically what you'll need to do is make your backend pattern-match expressions 308 fix a lot of code in the backend, with GEP lowering being only a small piece of