Displaying 2 results from an estimated 2 matches for "c587325e".
Did you mean:
587325
2012 Oct 19
0
[LLVMdev] How to represent __attribute__((fastcall)) functions in the IL
...> LLVM Developers mailing list
> 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/20121019/c587325e/attachment.html>
2012 Oct 19
4
[LLVMdev] How to represent __attribute__((fastcall)) functions in the IL
Functions with __attribute__((fastcall)) pop their arguments and take
up to two arguments in ecx and edx. Currently we represent them by
just setting the x86_fastcallcc calling convention. The problem is
that the ABI has some strange conventions on when a register is used
or not. For example:
void __attribute__((fastcall)) foo1(int y);
will take 'y' in ecx, but
struct S1 {
int x;
};