[PATCH] Generate better location ranges for some register-described variables.

Eric Christopher echristo at gmail.com
Thu May 29 18:22:10 PDT 2014


We could do something similar to the prologue and actually require
(well, try to require) backends to annotate epilogue instructions
appropriately.

It's probably the easiest idea at least.

-eric

On Thu, May 29, 2014 at 6:14 PM, Alexey Samsonov <vonosmas at gmail.com> wrote:
> Yes... I don't know a good way to find out what the function epilogue is at this stage. Current code will work for frame pointer and stack pointer if we are lucky enough and epilogue is actually the last machine basic block in the function (it is so for the simple cases).
>
> http://reviews.llvm.org/D3933
>
>
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits




More information about the llvm-commits mailing list