This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Omit frame pointer and fix %ebp by default on x86(take 3)
- From: Jeffrey A Law <law at redhat dot com>
- To: Roger Sayle <roger at eyesopen dot com>
- Cc: Jakub Jelinek <jakub at redhat dot com>, Andrew Haley <aph at redhat dot com>, gcc-patches at gcc dot gnu dot org, Richard Henderson <rth at redhat dot com>
- Date: Mon, 16 Aug 2004 23:02:08 -0600
- Subject: Re: [PATCH] Omit frame pointer and fix %ebp by default on x86(take 3)
- Organization: Red Hat, Inc
- References: <Pine.LNX.4.44.0408161318070.22769-100000@www.eyesopen.com>
- Reply-to: law at redhat dot com
On Mon, 2004-08-16 at 13:26, Roger Sayle wrote:
> On Mon, 16 Aug 2004, Jakub Jelinek wrote:
> It's my understanding that none of the GCC compilers themselves
> require the functionality of backtrace, the GDB executable doesn't
> require it, the Linux kernel doesn't require it, none of the
> applications in the SPEC benchmark suite require it, none of
> OpenEye's applications require it. It's easy to list the people
> who suffer from preserving the frame-pointer, is it only Java
> folks that are causing this performance hold-up?
Do the new versions of oprofile need this data? They have some
limited capability to get backtraces when events occur and I thought
it used the frame pointer to do that (otherwise we'd have to do
something ugly like embed a dwarf2 frame unwinder into the kernel and
run it when events occur -- not good).
jeff