[llvm-bugs] [Bug 28934] LLVMRunFunction does not work properly with MCJIT

via llvm-bugs llvm-bugs at lists.llvm.org
Thu Aug 11 09:33:07 PDT 2016


https://llvm.org/bugs/show_bug.cgi?id=28934

Lang Hames <lhames at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Lang Hames <lhames at gmail.com> ---
Hi Henning,

Some history to explain the current state of things: ExecutionEngine's
interface has always been the union of the functionality provided by the
Interpreter, the JIT (now deleted), and MCJIT. LLVMRunFunction shouldn't be
deprecated as it still works for the Interpreter, but I have added comments to
ExecutionEngine.h explaining the limitations when using MCJIT, and I have
changed MCJIT::runFunction to abort with a meaningful error at runtime if
called with unsupported arguments (r278348).

The underlying problem was the decision to try to support all execution engine
features in a single interface. The ORC APIs (LLVM's next generation of JIT
APIs) avoid this problem by breaking away from the ExecutionEngine interface.
If you want to check out the new APIs you'll find a tutorial series (under
development) at: http://llvm.org/docs/tutorial/BuildingAJIT1.html . The headers
are in include/llvm/ExecutionEngine/Orc, and some simple C bindings are
available at include/llvm-c/OrcCBindings.h .

Cheers,
Lang.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20160811/dc43cbfb/attachment.html>


More information about the llvm-bugs mailing list