I noticed it would still be a good idea to add an extra barrier in the epilog
as the
scheduler doesn't appear to handle aliases of frame accesses properly.
This patch simplifies the handling of the EH return value. We force the use of
the
frame pointer so the return location is always at FP + 8
Ping
I noticed it would still be a good idea to add an extra barrier in the epilog
as the
scheduler doesn't appear to handle aliases of frame accesses properly.
This patch simplifies the handling of the EH return value. We force the use of
the
frame pointer so the return location is always at
Wilco Dijkstra writes:
> Ping
>
> I noticed it would still be a good idea to add an extra barrier in the epilog
> as the
> scheduler doesn't appear to handle aliases of frame accesses properly.
>
> This patch simplifies the handling of the EH return value. We force the use
> of the
> frame poi
Jiong Wang wrote:
> The -fomit-frame-pointer is really broken on aarch64_find_eh_return_addr
Yes, that's a good conclusion. However even with the frame pointer there are
cases that fail, for example it will access LR off SP even after alloca. In fact
we're lucky it works at all sometimes...
> I
Ping
I noticed it would still be a good idea to add an extra barrier in the epilog
as the
scheduler doesn't appear to handle aliases of frame accesses properly.
This patch simplifies the handling of the EH return value. We force the use of
the
frame pointer so the return location is always a
On 10/08/16 17:26, Wilco Dijkstra wrote:
> I noticed it would still be a good idea to add an extra barrier in the epilog
> as the
> scheduler doesn't appear to handle aliases of frame accesses properly.
>
> This patch simplifies the handling of the EH return value. We force the use
> of the
>
