C++ binary compatibility between GCC 3.1 and GCC 3.2?

[Gabriel Dos Reis]

"Joseph S. Myers" <jsm28@cam.ac.uk> writes:

| On Thu, 4 Jul 2002, Andreas Jaeger wrote:
| 
| > What will this mean for distributions and for production usage of GCC
| > 3.1?  I fear this means that folks cannot easily upgrade from GCC 3.1
| > to GCC 3.2 since C++ is incompatible and all C++ libraries that are
| > needed for development need to be relinked.
| 
| Where does libstdc++ fit into this?

The library is not covered by the ABI requirement; but we try hard to
retain ABI compatibility.  

|  Is libstdc++ yet ready to be binary
| compatible between successive major releases?

No, we're currently far from that -- but we're striving for that goal.

|  If not, how useful is
| binary compatibility of the underlying C++ ABI?

People have been using third-party libary in place of libstdc++-v3.
Also, most of codes in libstc++-v3 are in headers (template
definitions) so the issue is less sensitive than with the compiler.

-- Gaby