gcc 3.x test matrix
H . J . Lu
hjl@lucon.org
Thu Sep 6 15:29:00 GMT 2001
On Fri, Sep 07, 2001 at 12:10:23AM +0200, Mark Kettenis wrote:
>
> I never said it would be easy. However, we can ask the gcc developers
> for the possible future changes in the libgcc_s.so ABI and make a new
> gcc based on gcc 3.0.x to try them out. We don't even have to make any
> real code changes, only the ABI changes.
>
> Changes to the frame info registration blackbox ABI
> (__register_frame_info*, __deregister_frame_info* and
> _Unwind_Find_FDE) will require changes in glibc. Richard has
> indicated that it's not very likely that such ABI changes are needed
> in the forseeable future. There is no point in "testing" such
> changes.
As I understand, the whole point of dlopening libgcc_s.so.1 is for
such changes.
>
> Other changes to the libgcc_s.so.1 ABI shouldn't affect glibc at all.
Why do we even need dlopening libgcc_s.so.1 in libc.so then? The one
in libc.so.6 should be as good as the one in any other libgcc_s.so.1.
H.J.
More information about the Libc-alpha
mailing list