Yuri wrote:
Mihai Donțu wrote:
I'm not sure, but I think tools such as google-perftools look at the
stack frames, which make the option '-fno-omit-frame-pointer' your
first pick. You can also try '-mprologue-epilogue'.
gcc-4.3.1 doesn't support an option -mprologue-epilogue on i586 platform.
And -fno-omit-frame-pointer didn't help.
gcc manual isn't clear on debugger-friendliness and doesn;t mention
prologue/epilogue much.
Yuri
Have you tried -fno-optimize-sibling-calls?
IIUC, this optimization is what allows one function to jump to another,
saving a stack frame under ideal conditions.
