[patches] Re: x86_64 frame unwind info

[Jan Hubicka]

> 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.

OK, what do you think is more sensible solution?
Basically our ABI specifies the unwind info, similar as IA-64 does. Unlike IA-64 we decided to use
dwarf2 and it can be nice to keep it same with the gcc one.

So solution I see is to invent new name for the unwind frame and add target macros to get gcc
write the eh-frame to that section and use it for unwinding in similar way as IA-64 machinery works.

Honza
> 
> 
> r~