[PATCH] AAPCS-VFP: Do not use any more VFP registers after allocating a CPRC to the stack

Renato Golin renato.golin at linaro.org
Thu Feb 6 14:26:45 PST 2014


Hi Oliver,

The patch looks good to me, though I'm not sure about the
CallingConvEmitter part.  It also looks correct, but I'll let other people
review that more thoroughly (Molloy?).

cheers,
--renato




On 6 February 2014 17:33, Oliver Stannard <oliver.stannard at arm.com> wrote:

> Hi,
>
>
>
> According the the AAPCS, if an argument is a CPRC (co-processor register
> candidate) but cannot be allocated to a co-processor register, the argument
> must be allocated on the stack and all co-processor registers of that class
> must be marked as unavailable (AAPCS, rule C.2.cp). However, llvm does not
> currently mark the VFP registers as unavailable, so can allocate a later
> CPRC to a register after an earlier one has been allocated to the stack.
>
>
>
> The attached patch corrects this.
>
>
>
> Oliver
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20140206/7b35019c/attachment.html>


More information about the llvm-commits mailing list