This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: How to force all functions to have full prologs and epilogs in optimized code?
- From: Mihai DonÈu <mihai dot dontu at gmail dot com>
- To: gcc-help at gcc dot gnu dot org, yuri at rawbw dot com
- Date: Wed, 8 Oct 2008 20:02:22 +0300
- Subject: Re: How to force all functions to have full prologs and epilogs in optimized code?
- References: <48ECE3A5.3090306@rawbw.com>
On Wednesday 08 October 2008, Yuri wrote:
> I debug an application and need to know which function calls were made.
> Many function though not inlined have optimized away epilogs, replaced
> by a jump.
> And google-perftools tool for example doesn't pick such functions up.
>
> Is there an option in gcc forcing it to emit full prologs/epilogs even
> for optimized code?
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'.
Check the gcc manual or the info pages for more 'debugging-friendly' options.
--
Mihai DonÈu
unices.bitdefender.com