This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: GCC 3.0 Release Criteria


>    - First, usually every system - even unknown - has a libc installed
>      somewhere around (which tries to be bincompatible as far as possible
>      - but read on). This is not generally the case with libstdc++, is
>      it? Solution: libstdc++.a.
> 
> Indeed!  Since the C++ ABI isn't really stable yet every major GCC
> release has a different libstdc++.so, and it is unlikely that every
> user has all of these installed.  Most distributions install a few of
> the most popular ones though.

This situation will end with 3.0.  That is, the 3.0 C++ ABI is intended
to be stable (on some platforms, it will be a multivendor ABI, meaning
that we can't change it because we don't control it).  This is one of
the release requirements.  (Fixes that are needed later will have to be
binary backward-compatible).



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]