"H.J. Lu" <hjl.to...@gmail.com> writes:
> Like this?
> Note that @option{-fno-omit-frame-pointer} doesn't force a new stack
> frame for all functions if it isn't otherwise needed, and hence doesn't
> guarantee a new frame pointer for all functions.
> Here is the updated patch with a note for -fno-omit-frame-pointer.
> OK for trunk?

I suspect there will be still some unwinder or code patching
setups which rely on frame pointer everywhere become broken. But
doing the optimization for -fno-omit-frame-pointer by default
seems reasonable.

I would add a new option
that gives the old -fno-omit-frame-pointer back, so that
users relying on frame pointers everywhere have a workaround.


Reply via email to