search for: lljitwithobjectcache

...ere is no chance of getting misleading assembly due to a compiler misconfiguration or persistent state bug. One way to dump object files, which works for both LLJIT and custom stacks, is to attach a dummy ObjectCache (see https://github.com/llvm/llvm-project/blob/master/llvm/examples/LLJITExamples/LLJITWithObjectCache/LLJITWithObjectCache.cpp) and dump the ObjBuffers that are passed in to the cache to disk. You can just return 'nullptr' from your dummy cache's getObject method, since you are not really using it as a cache. Alternatively, If you are writing a custom ORC stack there is a second option...

Using llvm 9, visual studio, HowToUseLLJIT.cpp It works fine in a release build. In a debug build It aborts due to an assert failure on Core.cpp (383) because the lhs flags are (Exported | Callable) and the rhs flags are (Callable). What mods should be made to fix this issue? Side note: The comments at the top reference HowToUseJIT.cpp rather than HotToUseLLJIT.cpp Thanks, Rob Conde

yeah i m concerned about jit compilation time.. On Sun, Jun 30, 2019 at 12:57 PM Praveen Velliengiri < praveenvelliengiri at gmail.com> wrote: > Yes I think so.. Could you please tell me in which context (compile time > improvement)? That is whether you are interested in knowing whether having > ORC instead of MCJIT, will increase your LLVM Build time or you are > concerned