This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/70238] [5/6 Regression] std::future_category ABI change
- From: "matz at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 15 Mar 2016 13:25:59 +0000
- Subject: [Bug libstdc++/70238] [5/6 Regression] std::future_category ABI change
- Auto-submitted: auto-generated
- References: <bug-70238-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70238
Michael Matz <matz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |matz at gcc dot gnu.org
--- Comment #4 from Michael Matz <matz at gcc dot gnu.org> ---
Well, I think one basic promise we try to make with our shared libs is that
it _can_ be upgraded in a system and it's expected to work. I don't think
experimental features should be allowed to deviate from that rule (for instance
many of the other parts of c++11 cared for this by either not providing symbols
in libstdc++.so at all or providing compatibility).
Basically our shared library (not just the object files) has a change in
one symbol, and we didn't bump either the symversion or the soname,
which I'd say is a bug (we can't fix anymore :-/ ).