This is the mail archive of the
mailing list for the GCC project.
Re: Switching the default for -fabi-version
- From: Michael Matz <matz at suse dot de>
- To: Allan Sandfeld <linux at sneulv dot dk>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 22 Oct 2003 16:14:44 +0200 (CEST)
- Subject: Re: Switching the default for -fabi-version
On Wed, 22 Oct 2003, Allan Sandfeld wrote:
> I really dont get the point of saying that libstdc++ differences gives a loss
> of backward compatibility. Isnt that what symbol versioning is for?
Is that one maintained thoroughly? I mean, even glibc sometimes forgets
to add this or that symbol for the right version. I have the feeling that
libstdc++ has a more complex namespace.
> I've never had problems with linking to two different versions of libstdc++
> through shared libraries. It's inefficient but it works!
No problems with the double construction of the global iostream stuff?
> Keeping the ABI stable would for KDE mean that old plugins and shared
> libraries could still be used, they would just load an additional
Yes, and exactly that made problems in the past. I have no idea if that
becomes better with the 3.3/3.4 combination, though.