PATCH: Share the dwarf2 unwind code between glibc and gcc 3.0
Richard Henderson
rth@redhat.com
Mon Jul 9 12:03:00 GMT 2001
On Mon, Jul 09, 2001 at 04:06:18PM +0200, Mark Kettenis wrote:
> IMHO HJ is heading down the wrong track. I don't see why we need to
> rip bits of code from both GCC 3.x and GCC 2.x. AFAICT the code in
> GCC 3.x (unwind-dw.c) is perfectly able to handle the frame info
> generated by GCC 2.x.
Indeed.
> It doesn't need to since mixing C++ code from GCC 2.x with C++ code
> from GCC 3.x isn't going to work, and just skips the GCC 2.x exception
> handler info.
Actually, it does. The issue is that __frame_state_for is intended
to be visible from glibc, which exports it to libstdc++-v2. So in
the end we're mixing C++ from 2.x and C from 3.x, which _is_ supposed
to work.
> >From a release engineering standpoint it would be great if my
> implementation of __frame_state_for could be added back to libgcc.
I agree.
r~
More information about the Libc-alpha
mailing list