[llvm-dev] Rationale for the object cache design?

[Paweł Bylica via llvm-dev]

I have the issue with the current ObjectCache API as well. I would like to
cache also the generation of IR modules from frontend code. I am able to
check if the cached object exists, but I still need to create a fake (but
valid) IR module and pass it to MCJIT. The MCJIT will then ask the
ObjectCache again to load the object.

Maybe the ObjectCache should allow using arbitrary cache key, not forcing
the module to be also the key.

On Thu, Aug 13, 2015 at 7:52 PM Antoine Pitrou via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

>
> Hello,
>
> I am a bit curious about the rationale for the current callback-based
> object cache API.  For Numba, it would be easier if there would be a
> simple procedural API:
> - one method to get a module's compiled object code
> - one method to load/instantiate a module from a given piece of object code
>
> I manage to get around the callback-based API to do what I want, but
> it's a bit weird to work with.  Would the above API suggestions be a
> desirable addition?
>
> PS: the gmane mirror for this list doesn't seem migrated yet, so I'm not
> sure this message will reach the list...
>
> Regards
>
> Antoine.
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org         http://llvm.cs.uiuc.edu
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160818/28868bfd/attachment.html>