[LLVMdev] Question about calling convention implementation in LLVM target

Herbie Robinson hrob at curbside-recording.com
Sat May 17 14:52:53 PDT 2014


Also, push and pop operations are slower on some architectures (I 
believe the x86_32 is one of them).  Smaller instructions are not always 
faster.

On 5/14/14 12:53 PM, Reid Kleckner wrote:
> To my knowledge, this is an open project.  It would also really help 
> with x86_32 codegen, but people care less and less about that as time 
> goes on.
>
>
> On Wed, May 14, 2014 at 4:05 AM, Rodolphe Suescun 
> <rsu.medal at dolphin.fr <mailto:rsu.medal at dolphin.fr>> wrote:
>
>     Hi,
>
>     We are currently developing an LLVM target for a micro-controller,
>     and would like our TargetLowering::LowerCall method to emit
>     PUSH instructions (instead of STORE) to pass arguments (which
>     would improve code density for function calls).
>
>     Is there a way of keeping track of the stack pointer changes
>     implied by the PUSH instruction to calculate the correct
>     offsets in RegisterInfo::eliminateFrameIndex when the call
>     sequence is generated ?
>
>     Thanks a lot in advance,
>     Rod
>     _______________________________________________
>     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
>
>
>
>
> _______________________________________________
> 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/20140517/811c5bf3/attachment.html>


More information about the llvm-dev mailing list