Shared library annoyance with gcc-3_0-branch

[H . J . Lu]

On Sun, Feb 18, 2001 at 12:39:12PM -0800, Mark Mitchell wrote:
> >>>>> "H" == H J Lu <hjl@valinux.com> writes:
> 
>     H> All I ask is a well-defined, stable ABI for shared libgcc so
>     H> that a shared libgcc from one gcc will work for all versions of
>     H> gcc. Can you tell me whom I should contact for my
>     H> suggestion/request?
> 
> I think we have that.
> 
> It could use a good deal more documentation, but there's no reason

I can live with a "libgccabi.h" which defines functions and data
structures exported by the ABI.

> that the ABI should change henceforth.
> 

If I fold libgcc in gcc 3.0 into glibc tody and change the gcc source
to use it instead its own, can I assume it will work with all future
versions of gcc from gcc 3.0? That is all the "well-defined, stable
ABI" about. Since you mentioned a different interface for EH, I can
change the gcc source to enable the new EH only if its support is
available from glibc.


H.J.