This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/52191] New: abi_check should flag additions to released versions
- From: "ro at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 09 Feb 2012 18:49:47 +0000
- Subject: [Bug libstdc++/52191] New: abi_check should flag additions to released versions
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52191
Bug #: 52191
Summary: abi_check should flag additions to released versions
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: ro@gcc.gnu.org
CC: bkoz@gcc.gnu.org
When regenerating the Solaris libstdc++ baselines, I noticed that there were
several additions to already release/closed symbol versions:
http://gcc.gnu.org/ml/gcc-patches/2012-01/msg01163.html
Provided that the baselines for the various targets are updated immediately
before
releases, abi_check should be able to flag such additions since they are
obviously
not supposed to happen. This is certainly far better than noticing the problem
only by accident/manual inspection or, even worse, only after another major
release has happened.
Ben, do you think this is feasible?
Thanks.
Rainer