search for: getpointertonamedfunctiononjitpool

...unction" to get native pointer on function. This function used the TheJit static pointer. To keep alive this functionality, I have added a static SmallVector<JIT*> JitPool (with its mutex JitPoolLock), which keep pointers of available JIT instance. A new static method on JIT object "getPointerToNamedFunctionOnJitPool" fills the need (iterate over available JIT to find the function). Attached you will find a test, based on "HowToUseJit" example, which instantiate 2 JIT, in eager/lazy mode and retrieve native pointer via getPointerToNamedFunction function. Where does it belong ? Should I add somet...

...native pointer on function. This function > used the TheJit static pointer. To keep alive this functionality, I have > added a static SmallVector<JIT*> JitPool (with its mutex JitPoolLock), which > keep pointers of available JIT instance. A new static method on JIT object > "getPointerToNamedFunctionOnJitPool" fills the need (iterate over available > JIT to find the function). > > Attached you will find a test, based on "HowToUseJit" example, which > instantiate 2 JIT, in eager/lazy mode and retrieve native pointer via > getPointerToNamedFunction function. Where does it bel...

...gt; function > > used the TheJit static pointer. To keep alive this functionality, I have > > added a static SmallVector<JIT*> JitPool (with its mutex JitPoolLock), > which > > keep pointers of available JIT instance. A new static method on JIT > object > > "getPointerToNamedFunctionOnJitPool" fills the need (iterate over > available > > JIT to find the function). > > > > Attached you will find a test, based on "HowToUseJit" example, which > > instantiate 2 JIT, in eager/lazy mode and retrieve native pointer via > > getPointerToNamedFuncti...

In eager compilation mode, I don't know of anything that would go wrong with having multiple JITs in the process. However, in lazy compilation mode, we need to map stub addresses to the JIT that knows how to compile them. Right now, that's done by looking up the static "TheJITResolver" variable and assuming it's the only JIT, but we could 1) use a static

Hi everyone ! If I call ExecutionEngine::createJIT (or EngineBuilder::create) more than one time, the second time fails on a assertion "Multiple JIT resolvers?". It seems that the JIT is designed to be a singleton in the process, and I was wondering if it was something mandatory. How hard will it be to make it a non-singleton object ? Is this a JIT-only problem (work needed on JIT