| /external/llvm/unittests/ExecutionEngine/Orc/ |
| D | OrcCAPITest.cpp | 83 LLVMOrcJITStackRef JIT = in TEST_F() local
88 LLVMOrcGetMangledSymbol(JIT, &testFuncName, "testFunc"); in TEST_F()
91 LLVMOrcAddEagerlyCompiledIR(JIT, wrap(M.get()), myResolver, nullptr); in TEST_F()
92 MainFnTy MainFn = (MainFnTy)LLVMOrcGetSymbolAddress(JIT, "main"); in TEST_F()
97 LLVMOrcRemoveModule(JIT, H); in TEST_F()
100 LLVMOrcDisposeInstance(JIT); in TEST_F()
107 LLVMOrcJITStackRef JIT = in TEST_F() local
112 LLVMOrcGetMangledSymbol(JIT, &testFuncName, "testFunc"); in TEST_F()
115 LLVMOrcAddLazilyCompiledIR(JIT, wrap(M.get()), myResolver, nullptr); in TEST_F()
116 MainFnTy MainFn = (MainFnTy)LLVMOrcGetSymbolAddress(JIT, "main"); in TEST_F()
[all …]
|
| /external/llvm/examples/Kaleidoscope/Orc/fully_lazy/ |
| D | README.txt | 6 Building on the lazy-irgen version of the tutorial, this version injects JIT
10 When a function definition is entered, a JIT callback is created and a stub
13 the indirect call is initialized to point at the JIT callback, and the compile
15 function and adds it to the JIT. The function pointer is updated by the JIT
17 calls to the stub will go straight to the body, not through the JIT.
|
| /external/mesa3d/src/gallium/auxiliary/gallivm/ |
| D | lp_bld_misc.cpp | 254 builder.setEngineKind(EngineKind::JIT) in lp_build_create_mcjit_compiler_for_module()
273 ExecutionEngine *JIT; in lp_build_create_mcjit_compiler_for_module() local
275 JIT = builder.create(); in lp_build_create_mcjit_compiler_for_module()
283 JIT = builder.create(builder.selectTarget(TT, MArch, MCPU, MAttrs)); in lp_build_create_mcjit_compiler_for_module()
285 if (JIT) { in lp_build_create_mcjit_compiler_for_module()
286 *OutJIT = wrap(JIT); in lp_build_create_mcjit_compiler_for_module()
|
| /external/llvm/docs/tutorial/ |
| D | LangImpl4.rst | 2 Kaleidoscope: Adding JIT and Optimizer Support
15 language, and adding JIT compiler support. These additions will
212 Adding a JIT Compiler
218 the code to an assembly file (.s) for some target, or you can JIT
222 In this section, we'll add JIT compiler support to our interpreter. The
229 In order to do this, we first declare and initialize the JIT. This is
247 The KaleidoscopeJIT class is a simple JIT built specifically for these
250 ``addModule`` adds an LLVM IR module to the JIT, making its functions
265 // JIT the module containing the anonymous expression, keeping a handle so
270 // Search the JIT for the __anon_expr symbol.
[all …]
|
| D | OCamlLangImpl4.rst | 2 Kaleidoscope: Adding JIT and Optimizer Support
15 language, and adding JIT compiler support. These additions will
139 (* Create the JIT. *)
169 The "``the_execution_engine``" variable is related to the JIT, which we
229 Adding a JIT Compiler
235 the code to an assembly file (.s) for some target, or you can JIT
239 In this section, we'll add JIT compiler support to our interpreter. The
246 In order to do this, we first declare and initialize the JIT. This is
254 (* Create the JIT. *)
258 This creates an abstract "Execution Engine" which can be either a JIT
[all …]
|
| /external/pcre/dist/ |
| D | RunTest.bat | 312 if %jit% EQU 1 call :runsub 1 testoutjit "Test with JIT Override" -q -s+
318 if %jit% EQU 1 call :runsub 2 testoutjit "Test with JIT Override" -q -s+
324 if %jit% EQU 1 call :runsub 3 testoutjit "Test with JIT Override" -q -s+
334 if %jit% EQU 1 call :runsub 4 testoutjit "Test with JIT Override" -q -s+
344 if %jit% EQU 1 call :runsub 5 testoutjit "Test with JIT Override" -q -s+
354 if %jit% EQU 1 call :runsub 6 testoutjit "Test with JIT Override" -q -s+
364 if %jit% EQU 1 call :runsub 7 testoutjit "Test with JIT Override" -q -s+
405 echo Test 12 Skipped due to absence of JIT support.
408 call :runsub 12 testout "JIT-specific features (JIT available)" -q
413 echo Test 13 Skipped due to presence of JIT support.
[all …]
|
| /external/pcre/dist/testdata/ |
| D | testoutput13 | 1 /-- This test is run only when JIT support is not available. It checks that an
3 are different without JIT. --/
12 JIT support is not available in this version of PCRE
|
| D | testinput13 | 1 /-- This test is run only when JIT support is not available. It checks that an
3 are different without JIT. --/
|
| D | testoutput12 | 1 /-- This test is run only when JIT support is available. It checks for a
2 successful and an unsuccessful JIT compile and save and restore behaviour,
3 and a couple of things that are different with JIT. --/
12 JIT study was successful
21 JIT study was not successful
31 JIT study was not successful
40 JIT study was not successful
49 JIT study was successful
69 Error -27 (JIT stack limit reached)
75 0: abcd (JIT)
[all …]
|
| /external/llvm/examples/BrainF/ |
| D | BrainFDriver.cpp | 54 JIT("jit", cl::desc("Run program Just-In-Time")); variable
101 if (!JIT) { in main()
139 if (JIT) { in main()
|
| /external/llvm/docs/ |
| D | DebuggingJITedCode.rst | 2 Debugging JIT-ed Code With GDB
29 In order to debug code JIT-ed by LLVM, you need GDB 7.0 or newer, which is
32 better option for debugging JIT-ed code on Mac OS X.
38 The emerging MCJIT component of LLVM allows full debugging of JIT-ed code with
42 Note that lli has to be passed the ``-use-mcjit`` flag to JIT the code with
43 MCJIT instead of the old JIT.
|
| D | HowToSubmitABug.rst | 151 which code generator you wish to compile the program with (e.g. LLC or the JIT)
167 can debug incorrect code generation by either LLC or the JIT, using
174 To debug the JIT:
192 debug the JIT, LLC, and CBE, using the pre-written Makefile targets, which
202 backend and the *test* file which either LLC or the JIT
224 #. If debugging the JIT, load the shared object and supply the test
|
| /external/llvm/lib/ExecutionEngine/ |
| D | ExecutionEngineBindings.cpp | 138 builder.setEngineKind(EngineKind::JIT) in LLVMCreateJITCompilerForModule()
141 if (ExecutionEngine *JIT = builder.create()) { in LLVMCreateJITCompilerForModule() local
142 *OutJIT = wrap(JIT); in LLVMCreateJITCompilerForModule()
197 builder.setEngineKind(EngineKind::JIT) in LLVMCreateMCJITCompilerForModule()
205 if (ExecutionEngine *JIT = builder.create()) { in LLVMCreateMCJITCompilerForModule() local
206 *OutJIT = wrap(JIT); in LLVMCreateMCJITCompilerForModule()
|
| /external/llvm/examples/OCaml-Kaleidoscope/Chapter7/ |
| D | toplevel.ml | 2 * Top-Level parsing and JIT Driver
36 (* JIT the function, returning a function pointer. *)
|
| /external/llvm/examples/OCaml-Kaleidoscope/Chapter5/ |
| D | toplevel.ml | 2 * Top-Level parsing and JIT Driver
36 (* JIT the function, returning a function pointer. *)
|
| /external/llvm/examples/OCaml-Kaleidoscope/Chapter6/ |
| D | toplevel.ml | 2 * Top-Level parsing and JIT Driver
36 (* JIT the function, returning a function pointer. *)
|
| /external/llvm/examples/OCaml-Kaleidoscope/Chapter4/ |
| D | toplevel.ml | 2 * Top-Level parsing and JIT Driver
36 (* JIT the function, returning a function pointer. *)
|
| /external/opencv3/modules/core/doc/ |
| D | cuda.markdown | 45 At the first call, the PTX code is compiled to binary code for the particular GPU using a JIT
46 compiler. When the target GPU has a compute capability (CC) lower than the PTX code, JIT fails. By
56 platforms, the PTX code for 1.3 is JIT'ed to a binary image. For devices with CC 1.1 and 1.2, the
57 PTX for 1.1 is JIT'ed. For devices with CC 1.0, no code is available and the functions throw
58 Exception. For platforms where JIT compilation is performed first, the run is slow.
|
| /external/llvm/examples/Kaleidoscope/MCJIT/lazy/ |
| D | README.txt | 7 to use the MCJIT execution engine instead of the older JIT engine.
14 The toy-jit.cpp file contains a version of the original JIT-based source code
|
| /external/llvm/examples/Kaleidoscope/MCJIT/complete/ |
| D | README.txt | 7 to use the MCJIT execution engine instead of the older JIT engine.
12 old JIT-based implementation, into a single file for easy comparison with
|
| /external/llvm/examples/Kaleidoscope/MCJIT/cached/ |
| D | README.txt | 7 to use the MCJIT execution engine instead of the older JIT engine.
15 The toy-jit.cpp file contains a version of the original JIT-based source code
|
| /external/llvm/bindings/ocaml/executionengine/ |
| D | llvm_executionengine.mli | 10 (** JIT Interpreter.
12 This interface provides an OCaml API for LLVM execution engine (JIT/
23 (** An execution engine is either a JIT compiler or an interpreter, capable of
|
| /external/llvm/include/llvm/Config/ |
| D | llvm-config.h.in | 86 /* Define if we have the Intel JIT API runtime support library */
89 /* Define if we have the oprofile JIT-support library */
|
| /external/llvm/tools/llvm-jitlistener/ |
| D | CMakeLists.txt | 1 # This tool is excluded from the CMake build if Intel JIT events are disabled.
|
| /external/llvm/unittests/ExecutionEngine/ |
| D | CMakeLists.txt | 17 # Include MCJIT tests only if native arch is a built JIT target.
|