[LLVMdev] Importance of VMKit JIT function cache
Sri
emdcdeveloper at gmail.com
Thu Apr 17 15:10:38 PDT 2014
Hi Gael
I am sorry that I couldn't explain what I was trying to say,
anyway I've got the answer :) . In the *parseFunction* method returns
*llvmfunction* pointer of compiled method and then it will be stored in
to cache. Could you please more elaborate on how those machine
instructions ( native functions) executing by llvm. I was trying trace
and I couldn't able to find out which component is taking those native
functions and execute them once its compiled.
Thank you for your help.
Regards
Sri.
On 04/17/2014 08:05 PM, Gaël Thomas wrote:
>
> Hi Sri,
>
> I think that I don't understand your question :) We have a cache.of
> compiled functions (native functions) and uses it to execute the Java
> code in the JIT. And, we do not keep the llvm representation of Java
> methods because we never reuse it (only in the AOT to generate the
> llvm bitcode file).
>
> I hope that it helps?
> Gaël
>
> Le 16 avr. 2014 14:19, "Sri" <emdcdeveloper at gmail.com
> <mailto:emdcdeveloper at gmail.com>> a écrit :
>
> Hi
> VMKit JIT has a function cache to store compiled IR code ,
> so, as soon as method is compiled , it will be stored in to
> function cache. My question is , who will use this compiled
> information from function cache. Since we are jitting , the
> llvm translate source code in to native code and executing them .
> So, how we relates this function cache with JIT ?
>
> Thanks
>
> Regards
> Sri.
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu <mailto:LLVMdev at cs.uiuc.edu>
> http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140417/ade1aaab/attachment.html>
More information about the llvm-dev
mailing list