On 24/07/14 13:25, Richard Earnshaw wrote:
On 22/07/14 15:52, Jiong Wang wrote:
currently we are generating sub-optimal epilogue when there
is frame pointer and there is outgoing area.
take gcc.target/aarch64/test_frame_12.c for example:
the epilogue for test_12 is:
On 22/07/14 15:52, Jiong Wang wrote:
> currently we are generating sub-optimal epilogue when there
> is frame pointer and there is outgoing area.
>
> take gcc.target/aarch64/test_frame_12.c for example:
>
> the epilogue for test_12 is:
>
>.L12:
>sub sp, x29, #1
On 22 July 2014 15:52, Jiong Wang wrote:
> gcc/
> * config/aarch64/aarch64.c (aarch64_expand_epilogue): Don't subtract
> outgoing area size when restore stack_pointer_rtx.
>
> gcc/testsuite/
> * gcc.target/aarch64/test_frame_12.c: Match optimized instruction
> sequences.
OK and committed.
currently we are generating sub-optimal epilogue when there
is frame pointer and there is outgoing area.
take gcc.target/aarch64/test_frame_12.c for example:
the epilogue for test_12 is:
.L12:
sub sp, x29, #16
ldp x29, x30, [sp, 16]
add sp, sp, 4
