Re: libgcc_s.so.1 ASIS won't work with glibc.

[Jakub Jelinek <jakub at redhat dot com>]

On Mon, Jul 02, 2001 at 05:36:40PM -0700, H . J . Lu wrote:
> I don't believe it will ever work since __register_frame,
> __register_frame_table, __register_frame_info_table and
> __register_frame_info have different ABIs in libgcc_s.so.1 and
> libc.so.6. You cannot use the same version, GLIBC_2.0, in
> libgcc_s.so.1. libgcc_s.so.1 should use GCC_3.0 for its verion of
> those functions since the ones in libgcc_s.so.1 won't work with
> the existing binaries compiled with g++ v2 dwarf2 frame based EH.
> glibc somehow has to provide the GLIBC_2.0 version of those functions
> if we want to support them in glibc compiled with gcc 3.0. One
> way to get it to work is we provide the backward compatible g++ v2
> dwarf2 frame based EH in libc.so.6 and let libgcc_s.so.1 provide the
> g++ v3 dwarf2 frame based EH. Did I miss something?

What do you mean by different ABIs?
Say __register_frame() is a function with void * which you should call
once for each library loaded with __EH_FRAME_BEGIN__, how can that be
possibly different?
Similarly __register_frame_info (although it takes struct object pointer,
you are not supposed to do anything with it after you passed it to that
function, the memory area pointed to by that pointer will be owned by
__register_frame_info implementation.
It is enough if glibc's __frame_state_for is built on top of
_Unwind_Find_FDE.

	Jakub