public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/57581] New: abi_tag vs. demangler
@ 2013-06-10 21:00 bkoz at gcc dot gnu.org
  2013-06-10 22:06 ` [Bug c++/57581] " schwab@linux-m68k.org
  2013-06-11 15:00 ` bkoz at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: bkoz at gcc dot gnu.org @ 2013-06-10 21:00 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57581

            Bug ID: 57581
           Summary: abi_tag vs. demangler
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bkoz at gcc dot gnu.org

Some member functions in libstdc++ have been decorated with the "abi_tag"
attribute.

Any abi_tag attribution renders these names unable to be demangled.

For instance:

      iterator
      erase(const_iterator __first, const_iterator __last)
      { return _M_t.erase(__first, __last); }

For set turns from:
_ZNSt3setIiSt4lessIiESaIiEE5eraseESt23_Rb_tree_const_iteratorIiES5_

into:
 _ZNSt3setIiSt4lessIiESaIiEE5eraseB5cxx11ESt23_Rb_tree_const_iteratorIiES5_


The first can be de-mangled into:
std::set<int, std::less<int>, std::allocator<int>
>::erase(std::_Rb_tree_const_iterator<int>, std::_Rb_tree_const_iterator<int>)

The second, not so much.


^ permalink raw reply	[flat|nested] 3+ messages in thread
* [Bug c++/57581] abi_tag vs. demangler
  2013-06-10 21:00 [Bug c++/57581] New: abi_tag vs. demangler bkoz at gcc dot gnu.org
@ 2013-06-10 22:06 ` schwab@linux-m68k.org
  2013-06-11 15:00 ` bkoz at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: schwab@linux-m68k.org @ 2013-06-10 22:06 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57581

--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
Try using a newer demangler.

$ ./cxxfilt
_ZNSt3setIiSt4lessIiESaIiEE5eraseB5cxx11ESt23_Rb_tree_const_iteratorIiES5_
std::set<int, std::less<int>, std::allocator<int>
>::erase[abi:cxx11](std::_Rb_tree_const_iterator<int>,
std::_Rb_tree_const_iterator<int>)


^ permalink raw reply	[flat|nested] 3+ messages in thread
* [Bug c++/57581] abi_tag vs. demangler
  2013-06-10 21:00 [Bug c++/57581] New: abi_tag vs. demangler bkoz at gcc dot gnu.org
  2013-06-10 22:06 ` [Bug c++/57581] " schwab@linux-m68k.org
@ 2013-06-11 15:00 ` bkoz at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: bkoz at gcc dot gnu.org @ 2013-06-11 15:00 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57581

Benjamin Kosnik <bkoz at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Benjamin Kosnik <bkoz at gcc dot gnu.org> ---
confirmed, it works, thanks!


^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-06-11 15:00 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-06-10 21:00 [Bug c++/57581] New: abi_tag vs. demangler bkoz at gcc dot gnu.org
2013-06-10 22:06 ` [Bug c++/57581] " schwab@linux-m68k.org
2013-06-11 15:00 ` bkoz at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).