[PATCH][llvm-c] Expose MC JIT

[Chris Lattner]

On Apr 22, 2013, at 10:06 AM, "Kaylor, Andrew" <andrew.kaylor at intel.com> wrote:

> The state management in MCJIT is quite sloppy right now.  I agree that invalidating the code cache is an issue that needs to be considered.  It seems to me that MCJIT itself ought to be able to do that when it needs to be done if it were paying attention.  At the very least, it could happen in the 'finalizeObject' method.  That's somewhat tangential to the patch at hand, but it is a consideration.  If there's something quick I can do to MCJIT to make this work, that's probably preferable to pushing something into the C-interface implementation.  I'll give that some thought today, but if anyone else is interested I'd be happy to make it a discussion rather than just a private rumination.
> 
> Otherwise, my main question about the patch has to do with the nature of the C-interface API.  Is that API treated as a contract that needs to be respected from release to release or are we free to tinker with it as needed?  The thing that worries me is how this interface will survive the transition to multiple module support.

We need to maintain it release to release, but it can change within a release (so for example, it can iterate, but locks down when 3.3 ships).

For the MCJIT specifically, since we know that there will be changes, it is probably enough to document the specific functions as experimental and subject to change.

-Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130422/ce2a635a/attachment.html>