[LLVMdev] EE, JIT, MCJIT class structure

Yaron Keren yaron.keren at gmail.com
Fri Oct 18 03:10:00 PDT 2013


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 and
the inheriting classes JIT and MCJIT exposing their specialized
functionality.

This requires exposing JIT and MCJIT headers, including a JITcreater and a
MCJITcreator or suitable constructors.

Yaron
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131018/30f02cde/attachment.html>


More information about the llvm-dev mailing list