[PATCH] PR 16373: -fomit-frame-pointer when optimizing on x86

[Giovanni Bajo]

Paolo Bonzini wrote:

>> I don't understand your distinction between code and data directly
>> supporting code execution.  If executable machine code size is the
>> only criterion, we could compile code to P-code and have almost zero
>> code size, but I fail to see how this would help those who struggle
>> with code size.
>
> Unwind data is never loaded from disk in the first place, it only
> wastes address space.  Read-only is shared between different
> "instances" of the same applications, and swapped to/from the on-disk
> binary rather than the swap file.

There are other systems than GNU/Linux, you know. Like embedded systems with no
MMU or without a smart enough OS. People who care about -Os usually want the
total binary ELF image to be as small as possible, because it needs to be burnt
in a flash, etc.

-fasynchronous-unwind-tables should be a no-no for -Os.
-- 
Giovanni Bajo