public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/42670] demangler doesn't completely demangle a global constructors symbol
Date: Sat, 09 Jan 2010 16:23:00 -0000	[thread overview]
Message-ID: <20100109162307.8004.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42670-5724@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from hjl dot tools at gmail dot com  2010-01-09 16:23 -------
libiberty/testsuite/demangle-expected has

---
--format=gnu-v3 --no-params
_GLOBAL__I__Z2fnv
global constructors keyed to _Z2fnv
global constructors keyed to _Z2fnv
---

Shouldn't it be

global constructors keyed to fn()


-- 

hjl dot tools at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |
            Summary|c++filt/nm --demangle       |demangler doesn't completely
                   |doesn't completely demangle |demangle a global
                   |a global constructors symbol|constructors symbol


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


  parent reply	other threads:[~2010-01-09 16:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-09 10:04 [Bug other/42670] New: c++filt/nm --demangle " debian-gcc at lists dot debian dot org
2010-01-09 10:19 ` [Bug other/42670] " paolo dot carlini at oracle dot com
2010-01-09 16:23 ` hjl dot tools at gmail dot com [this message]
2010-01-09 18:16 ` [Bug other/42670] demangler " ian at airs dot com
2010-01-09 18:43 ` [Bug other/42670] demangler doesn't completely demangle a global constructor symbol hjl dot tools at gmail dot com
2010-01-09 19:07 ` paolo dot carlini at oracle dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100109162307.8004.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).