search for: setjitmemorymanag

...ace to LLVM where it can store the results. > > Yes, you should be able to inherit from llvm::JITMemoryManager and do something like this. I've been trying to work with this solution, but it does pose a problem. The problem is that we use an ExecutionEngine and set a memory manager with setJITMemoryManager on EngineBuilder. The problem is that this means when the ExecutionEngine is deallocated, it end up deallocating the memory manager. I can understand doing this when the code sets up it's own memory manager, but with an external memory manager, I'd expect LLVM not to deallocate that obje...

...pace to LLVM where it can store the results. > > Yes, you should be able to inherit from llvm::JITMemoryManager and do something like this. I've been trying to work with this solution, but it does pose a problem. The problem is that we use an ExecutionEngine and set a memory manager with setJITMemoryManager on EngineBuilder. The problem is that this means when the ExecutionEngine is deallocated, it end up deallocating the memory manager. I can understand doing this when the code sets up it's own memory manager, but with an external memory manager, I'd expect LLVM not to deallocate that obje...

...nd I've run into some trouble. Here's how I'm setting up the ExecutionEngine for the MCJIT case: m_llvm_exec = llvm::EngineBuilder(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...

...ere it can store the results. > > > > Yes, you should be able to inherit from llvm::JITMemoryManager and do something like this. > I've been trying to work with this solution, but it does pose a problem. The problem is that we use an ExecutionEngine and set a memory manager with setJITMemoryManager on EngineBuilder. The problem is that this means when the ExecutionEngine is deallocated, it end up deallocating the memory manager. > I can understand doing this when the code sets up it's own memory manager, but with an external memory manager, I'd expect LLVM not to deallocate that...

On Mon, Jan 14, 2013 at 4:56 AM, Dirkjan Bussink <d.bussink at gmail.com>wrote: > Hello all, > > I've already bothered people on IRC with this question and it was > recommended to ask it here. > > First of all, some context. In Rubinius (http://rubini.us/, > http://github.com/rubinius/rubinius) we use LLVM for our JIT. We create > LLVM IR using the C++ API and

...ext); - RJMM = new RecordingJITMemoryManager; + RJMM = CreateMemoryManager(); RJMM->setPoisonMemory(true); std::string Error; + TargetOptions Options; + Options.JITExceptionHandling = true; TheJIT.reset(EngineBuilder(M).setEngineKind(EngineKind::JIT) .setJITMemoryManager(RJMM) - .setErrorStr(&Error).create()); + .setErrorStr(&Error) + .setTargetOptions(Options).create()); ASSERT_TRUE(TheJIT.get() != NULL) << Error; } @@ -292,6 +299,46 @@ EXPECT_EQ(3, *GPtr); } +// Regression test for a...

On Aug 21, 2012, at 2:12 PM, Michael Muller <mmuller at enduden.com> wrote: > > Hi, I found a bug in the code that generates exception tables, I've attached > what I think is the correct fix. > > When you run out of space writing to a buffer, the buffer management code > simply stops writing at the end of the buffer. It is the responsibility of > the caller to

Eric Christopher wrote: > > On Aug 21, 2012, at 2:12 PM, Michael Muller <mmuller at enduden.com> wrote: > > > > > Hi, I found a bug in the code that generates exception tables, I've attached > > what I think is the correct fix. > > > > When you run out of space writing to a buffer, the buffer management code > > simply stops writing at the

...ostic Err; LLVM_Module = new llvm::Module("LLVM Test", *LLVM_Context); if (!LLVM_Module) { Err.print(argv[0], llvm::errs()); return 1; } std::string ErrorMsg; llvm::EngineBuilder builder(LLVM_Module); builder.setErrorStr(&ErrorMsg); builder.setJITMemoryManager(llvm::JITMemoryManager::CreateDefaultMemManager()); builder.setEngineKind(llvm::EngineKind::JIT); //CodeGenOpt::Level OLvl = CodeGenOpt::Default; //builder.setOptLevel(OLvl); llvm::TargetOptions Options; Options.JITExceptionHandling = false; Options.JITEmitDebugInfo = f...

Hello all, I've already bothered people on IRC with this question and it was recommended to ask it here. First of all, some context. In Rubinius (http://rubini.us/, http://github.com/rubinius/rubinius) we use LLVM for our JIT. We create LLVM IR using the C++ API and turn that into machine code using ExecutionEngine::runJITOnFunction. The resulting native code is then installed as the