Another point worth mentioning is that, we are using our executable in busy-box style i.e. we have one single executable which is sym-linked to various other programs and program behaves appropriately based on argv[0]. I thought -fPIC was for shared-libraries. Is -fPIC applicable for executables as well ? On Mon, Jul 1, 2013 at 11:13 AM, vijay nag <vijunag@xxxxxxxxx> wrote: > I just RTFM pages of gcc and I see that -Os will enable > -fomit-frame-pointer. Is it possible to not omit frame-pointer while > the optimization > level is -O1 ? > > [P.S: F = Fine] > > On Sun, Jun 30, 2013 at 4:25 PM, Andrew Haley <aph@xxxxxxxxxx> wrote: >> On 06/30/2013 07:23 AM, vijay nag wrote: >>> Binary compiled with GCC-4.7.2 has a different epilogue/prologue >>> sequence when compared with the same binary emitted by GCC-3.3.6. >> >> Well, yes. A lot of work has been done on GCC since 2005. >> >>> I'm sure I haven't used fomit-frame-pointer compilation flag. What >>> could be the issue here ? Is the linker doing some optimization >>> here? It has rendered my executable undebuggable in gdb. >> >> This must be a GDB problem, then. It all looks perfectly reasonable. >> Which GDB is this? >> >> Andrew. >>
