This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Vtable incompatibility between GCC 3.0/3.2?
Andreas Jaeger wrote:
[...]
NOte the 3.3 libstdc++ is only upward compatible, you cannot build a
program with the 3.3 libstdc++ and run it with a 3.2 one - the other
way round works. In general (unless you hit that bug I mentioned),
objects compiled with 3.2 should work with 3.3.
Was there a reason not to reflect this incompatibility (3.3 built code
does not work with 3.2 libstdc++) in the versions of the symbols
exported by libstdc++? For example:
- symbol XXX is exported with version GLIBCPP_3.2 in the 3.2 libstdc++;
- in 3.3 libstdc++, the implementation of XXX changed in an upward
compatible way;
- shouldn't XXX be versioned with GLIBCPP_3.2 and GLIBCPP_3.3 in 3.3
libstdc++, something like
__asm__(".symver XXX,XXX@GLIBCPP_3.2");
__asm__(".symver XXX,XXX@@GLIBCPP_3.3");
Just a thought,
-Stephan
Yes, making a web page out of this would be fine,
Andreas