Lines Matching full:backend
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
983 To perform this pattern match, the PowerPC backend includes the following
1014 and related ``tblgen`` classes in the PowerPC backend.
1630 compiler backend, LLVM also fully supports building a native assembler.
1722 backend, XOR8rr has two input GR8's and one output GR8 (where an input is tied
1980 The ARM backend has basic support for integer code in ARM codegen mode, but
2018 Basic support exists on the X86 backend. Currently vararg doesn't work and the
2113 The X86 backend
2124 backend. This is not an exhaustive list, and it would be useful to add those
2144 The following target-specific calling conventions are known to backend:
2234 The PowerPC backend
2408 The NVPTX backend
2453 The extended Berkeley Packet Filter (eBPF) backend
2642 The AMDGPU backend
2652 backend.
2682 AMDGPU Backend generates *Elf64_Rela* relocation records with the following
