This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/66438] libstdc++ 5.1 broke binary compat with old code using std::error_category
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 06 Jun 2015 13:13:35 +0000
- Subject: [Bug libstdc++/66438] libstdc++ 5.1 broke binary compat with old code using std::error_category
- Auto-submitted: auto-generated
- References: <bug-66438-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66438
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to James Y Knight from comment #5)
> The *one and only purpose* of the file
> libstdc++-v3/src/c++11/compatibility-c++0x.cc is to provide binary
> compatibility for c++11 binaries compiled against older libstdc++ versions,
> and now running against a newer one.
It ensures they will still link.
> If libstdc++.so.6, version 5.1, is not supposed to work properly with c++
> binaries compiled by the 4.9 compiler, it should not be providing these
> compatibility symbols at all.
I would prefer that, but it's not our policy.
> Since it does provide them, there is clearly intent to provide compatibility
I didn't realise you were the maintainer and knew what's supposed to work.
Oh wait, you're not :-)