search for: removemoduleprovider

...("emptyModule"); ExecutionEngine executionEngine = ExecutionEngine::create(emptyModule); ExistingModuleProvider moduleProvider = new ExistingModuleProvider(module from disk); executionEngine->addModuleProvider(); ////tests executionEngine->removeModuleProvider delete executionEngine ExecutionEngine executionEngine = ExecutionEngine::create(emptyModule); ExistingModuleProvider moduleProvider = new ExistingModuleProvider(module from disk); executionEngine->addModuleProvider(); ////tests execut...

...d. This is a bit inconvenient especially since I have to generate new functions at irregular times. I'm not too keen on using the non-standard _expand function to resize memory to the right size. Anyway, I also noticed that it's also possible to do the following: executionEngine->removeModuleProvider(moduleProvider); delete moduleProvider; module->dropAllReferences(); delete module; This way the memory overhead of the IR of the function is removed and the executionEngine stays around for further use and still manages the memory of the binary functions. So is this a sane approac...

...tion in module A. I use new llvm::Function(type, llvm::Function::ExternalLinkage, "myLinkedFunction", moduleB) when I am defining the function with its body in module B. I then have an ExecutionEngine which I constructed with an empty dummy module so that I can use addModuleProvider and removeModuleProvider to link arbitrary modules later. I call addModuleProvider with module A and module B wrapped in ExistingModuleProviders, and call getPointerToFunction. Any ideas? If there isn't anything obviously wrong here, I can boil this down to a snippet that reproduces the problem. Thanks, Aaron Bil...

When JITEmitter is teared down, it also deletes the JITMemoryManager instance. That in turns release the memory of the generated functions. Is this what you are referring to? The DefaultJITMemoryManager is pretty simple. You can obviously write your own memory manager class that maps the memory in a way that's persistent. Then all you have to do is to pass a handle of it to

Hi all, I'm using LLVM to generate a fairly large number of separate functions at run-time. To minimize the memory overhead, I'd like to delete the IR and everything else that is no longer needed after a function has been generated (I don't use lazy compilation or anything like that). I noticed that deleting the ExecutionEngine deletes everything (Module, Function(s),