Displaying 2 results from an estimated 2 matches for "d09a0d18".
2013 Oct 18
0
[LLVMdev] EE, JIT, MCJIT class structure
Yes, we've been planning to separate the execution engines for a while now, and we've made some small steps (such as breaking out the RTDyldMemoryManager interface) in preparation for doing so. There are some serious entanglements, not least of which there are MCJIT clients (LLDB, for instance) which are using memory managers derived from the JITMemoryManager. Eventually (and soon)
2013 Oct 18
2
[LLVMdev] EE, JIT, MCJIT class structure
The functionality of MCJIT vs JIT had diverged.
Not only they have different operating models (lazy function vs.
multi-module), the API is almost completely different. There is a set of
functions just for JIT, another set of functions just for MCJIT, with
comments saying which ones work for JIT and which ones work for MCJIT.
It would make sense for the EE to have only the shared functionality