https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88125
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Yes, I think we can just remove the 3.4.6 pattern. It's not doing anything.
My checker script finds this issue:
$ echo _ZNKSt15basic_stringbufIwSt11char_traitsIwESaIwEE3strEv |
../../scripts/symverck.py config/abi/pre/gnu.ver
Symbol matches:
_ZNKSt15basic_stringbufIwSt11char_traitsIwESaIwEE3strEv
std::basic_stringbuf<wchar_t, std::char_traits<wchar_t>,
std::allocator<wchar_t> >::str() const
GLIBCXX_3.4 _ZNKSt15basic_stringbufIwSt11char_traitsIwESaIwEE3strEv
(line 359)
GLIBCXX_3.4.6 _ZNKSt15basic_stringbufIwSt11char_traitsIwESaIwEE3strEv
(line 1152)
But I just tend to only use it for finding problems with specific symbols, not
a sweep over the whole ABI. I should try doing that.
