Displaying 4 results from an estimated 4 matches for "use_mcjit".
2014 Jan 20
2
[LLVMdev] MCJIT versus getLazyBitcodeModule?
...ineBuilder(module())
.setEngineKind(llvm::EngineKind::JIT)
.setErrorStr(err)
.setJITMemoryManager(jitmm())
.setOptLevel(llvm::CodeGenOpt::Default)
.setUseMCJIT(USE_MCJIT)
.create();
USE_MCJIT is 1 when I'm building the code to use MCJIT. I'm initializing the buffer and seeding it with the precompiled bitcode in the same way as always, as outlined above.
The basic problem is that it's not finding the symbols in that bitcode....
2013 Jun 03
5
[LLVMdev] MCJIT and Kaleidoscope Tutorial
...idoscope Tutorial (toy.cpp from
llvm/examples/Kaleidoscope/Chapter7, LLVM 3.3 release branch) in order
to use MCJIT instead of JIT. I get segmentation fault when running
toy.cpp with fibonacci example from the tutorial. My modified toy.cpp is
in attachment and still works with JIT (when #define USE_MCJIT line is
commented out).
I read discussions regarding MCJIT in this mailing list, and I
understand it that MCJIT currently cannot be used in the same way as
JIT. The separate function-by-function (i.e. incremental) compilation
approach with getPointerToFunction, like the one used in the
Kaleid...
2013 Jun 04
0
[LLVMdev] MCJIT and Kaleidoscope Tutorial
...Kaleidoscope Tutorial (toy.cpp from llvm/examples/Kaleidoscope/Chapter7, LLVM 3.3 release branch) in order to use MCJIT instead of JIT. I get segmentation fault when running toy.cpp with fibonacci example from the tutorial. My modified toy.cpp is in attachment and still works with JIT (when #define USE_MCJIT line is commented out).
I read discussions regarding MCJIT in this mailing list, and I understand it that MCJIT currently cannot be used in the same way as JIT. The separate function-by-function (i.e. incremental) compilation approach with getPointerToFunction, like the one used in the Kaleidoscop...
2013 Jun 04
1
[LLVMdev] MCJIT and Kaleidoscope Tutorial
...Kaleidoscope Tutorial (toy.cpp from llvm/examples/Kaleidoscope/Chapter7, LLVM 3.3 release branch) in order to use MCJIT instead of JIT. I get segmentation fault when running toy.cpp with fibonacci example from the tutorial. My modified toy.cpp is in attachment and still works with JIT (when #define USE_MCJIT line is commented out).
>
> I read discussions regarding MCJIT in this mailing list, and I understand it that MCJIT currently cannot be used in the same way as JIT. The separate function-by-function (i.e. incremental) compilation approach with getPointerToFunction, like the one used in the Ka...