This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Slightly less trivial clean-up patch for stl_tree
- From: Paolo Carlini <pcarlini at suse dot de>
- To: Gawain Bolton <gp dot bolton at computer dot org>
- Cc: libstdc++ <libstdc++ at gcc dot gnu dot org>
- Date: Tue, 01 Aug 2006 21:23:03 +0200
- Subject: Re: Slightly less trivial clean-up patch for stl_tree
- References: <44CA5033.7030505@computer.org> <44CA5598.6050303@suse.de> <44CA5CCB.8000907@computer.org> <44CA60AD.5000609@suse.de> <44CB390D.2020708@computer.org> <44CB4455.7030809@suse.de> <44CFA7C8.3060706@computer.org>
Gawain Bolton wrote:
You're implying that the linker sees objects produced from different
versions of GCC. It's not realistic to maintain arbitrary object
level compatibility across different versions of the compiler, and I
would hope that libraries contain all template instatiations so that
this type of internal change is not a problem for third party libraries.
Maybe not realistic according to your personal judgment, but we are
striving to maintain it, with rather good results so far.
In this particular case the problem could be circumvented by renaming
_M_insert_equal() and _M_insert_unique() and changing stl_map.h,
stl_multimap.h, stl_set.h and stl_mutlset.h to use the new function.
Since I will certainly not provide such a horrid patch,
again, horrid accordind to your personal taste. Of course, a more
elegant solution is welcome, and I will work on it, in case.
I have, nor could find, any info on the v7-branch.
Strange, the branch is correctly mentioned in:
http://gcc.gnu.org/svn.html
Anyway, ABI breaking changes go there and regular contributors know
about it.
Thanks,
Paolo.