Displaying 3 results from an estimated 3 matches for "5b0ca6f8".
2009 Dec 16
1
[LLVMdev] code generation for calls in JITted code after r88984
...ist
> > 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/20091216/5b0ca6f8/attachment.html>
2009 Dec 15
0
[LLVMdev] code generation for calls in JITted code after r88984
On Tue, Dec 15, 2009 at 1:05 AM, Zoltan Varga <vargaz at gmail.com> wrote:
> Hi,
>
> After this commit:
> http://llvm.org/viewvc/llvm-project?view=rev&revision=88984
>
> the X86 JIT no longer emits calls using call <ADDR>, but always uses mov
> REG, <ADDR>, call *REG.
That should only be the x86-64 JIT. If the x86-32 JIT does that, it's
definitely a
2009 Dec 15
3
[LLVMdev] code generation for calls in JITted code after r88984
Hi,
After this commit:
http://llvm.org/viewvc/llvm-project?view=rev&revision=88984
the X86 JIT no longer emits calls using call <ADDR>, but always uses mov
REG, <ADDR>, call *REG. This causes problems for the usage of LLVM in JITs
since the JIT can no longer patch the callsite after the callee have been
compiled. According to the comments for the commit, this was done to fix the