This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [discuss] Re: [patches] Re: x86_64 frame unwind info
- To: Richard Henderson <rth at redhat dot com>
- Subject: Re: [discuss] Re: [patches] Re: x86_64 frame unwind info
- From: Geert Bosch <bosch at gnat dot com>
- Date: Thu, 18 Oct 2001 14:12:02 -0400 (EDT)
- Cc: Andi Kleen <ak at suse dot de>, Jan Hubicka <jh at suse dot cz>,gcc-patches at gcc dot gnu dot org, patches at x86-64 dot org, discuss at x86-64 dot org
On Wed, 17 Oct 2001, Richard Henderson wrote:
On Wed, Oct 17, 2001 at 09:41:48PM +0200, Andi Kleen wrote:
> So turning the space overhead from 10-20% to 20-40% for C++. Does not look
> very attractive. I would strongly advocate to not duplicate them at least
> for x86-64.
I don't like this much at all. The format of .eh_frame is private to
gcc and libgcc, and won't match what a dwarf2 debugger expects to see.
The format of the EH frame for x86-64 is not private, but standardized.
If DWARF extensions are needed, they should be added to the ABI standard.
This has been discussed during the design phase of the x86-64 ABI.
Since it is expected that programs and libraries on x86-64 will not use
a fixed frame poiner, but still need the ability to unwind stack frames
for either debugging, garbage collection, exception handling or other
purposes, it was decided to standardize on the format of the unwind
information.
-Geert