This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libsupc++
- To: "David O'Brien" <obrien at Freebsd dot org>
- Subject: Re: libsupc++
- From: Phil Edwards <pedwards at disaster dot jaj dot com>
- Date: Thu, 21 Dec 2000 19:07:38 -0500
- Cc: gcc at gcc dot gnu dot org
- References: <20001221155144.L10490@dragon.nuxi.com>
On Thu, Dec 21, 2000 at 03:51:45PM -0800, David O'Brien wrote:
> What exactly is libsupc++ (part of libstdc++-v3)? Unfortunately there is
> no README, and as usual the CVS logs only tell the what, not the _why_.
>
> What does "sup" stand for? Is there a reason this code isn't just linked
> into libstdc++?
"C++ support".
It contains the routines for exception handling, among other things. It all
got broken out of libgcc (where it used to live) so that one library could
be changed independantly of the other.
There are two reasons (that I can think of, at least) why it isn't just
part of libstdc++ itself:
1) Programs which don't use the standard library shouldn't necessarily
be forced to link against libstdc++. If it's a static link, the binary
is *huge*. libsupc++ supports the core language itself and is small.
2) For the same reason that glibc and solaris moved to several smaller
shared libraries rather than one large libc.so -- individual libs can
be replaced easier.
Phil
--
pedwards at disaster dot jaj dot com | pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools. Fools are protected by more capable fools.