Problems with exception handling in glibc and gcc.

[Ulrich Drepper]

Jason Merrill <jason@redhat.com> writes:

> No.  These interfaces are internal to libgcc and should not be
> restricted.  The proper fix is to stop exporting these functions from
> glibc.  There's no reason to do that.  Really, there's no reason for
> them to be in glibc at all, but at the very least they should be
> hidden.

The problem is that they are there because when glibc 2.0 released we
had no symbol versioning or other possibilities to restrict the export
list.

> I don't suppose there's any way to suppress them in currently
> installed glibcs?

Not without breaking programs.

Therefore the proposal to introduce a new ABI and leaving the old
around seems like a good idea.

-- 
---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------