Re: gcc: optimizations, and stack traces

[Joerg Sonnenberger <joerg%bec.de@localhost>]

On Sun, Feb 11, 2018 at 04:13:56PM +0700, Robert Elz wrote:
>     Date:        Sun, 11 Feb 2018 09:11:45 +0100
>     From:        Maxime Villard <max%m00nbsd.net@localhost>
>     Message-ID:  <2c83e9d9-f49c-479b-7a4c-1df581a2bb57%m00nbsd.net@localhost>
> 
>   | So we have the same problem, and we need to find a way
>   | to tell GCC to always push the frame at the beginning of the functions.
> 
> Either that or the stack unwind code needs to become smarter - which
> would be a better solution, as it avoids dropping (the admittedly minor)
> benefit  obtained from deferring the frame pointer update (which to be a
> useful solution would need to be universal) and adds a (not insignificant)
> cost to the stack unwind code - but performance there usually does
> not matter.

Again, the logic for that already exists. -fomit-frame-pointer would not
be acceptable otherwise.

Joerg