Re: Inhibit saving callee-saved registers for noreturn+nothrow functions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Segher Boessenkool:

> Hi!
>
> On Mon, Oct 14, 2019 at 11:26:15AM +0200, Florian Weimer wrote:
>> In some cases, it is desirable as an optimization not to save any
>> callee-saved registers in the function prologue.  This is common for
>> functions which are at the lowest frame, where there is nothing to
>> return to, and unwinding cannot proceed, either.  However, GCC seems to
>> generate code for saving registers even for such functions, for example:
>
>> Is there a way to avoid this?
>
> I don't think so.
>
> What will this do to debuggability?  Not much I hope...  There are many
> comparable cases where we lose variable contents of callers.

The values saved belong to the caller's frame.  If we know that such a
frame does not exist, there can't be a debugging regression because the
values are meaningless.

> Could you open a feature request please?

I filed: <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92086>

Thanks,
Florian



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux