public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drow at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/13447] New: Another demangler problem with method cv-qualifiers Date: Fri, 19 Dec 2003 16:32:00 -0000 [thread overview] Message-ID: <20031219155953.13447.drow@gcc.gnu.org> (raw) Try demangling this name: _ZZN8CryptoPP7NullRNGEvENK7NullRNG13AlgorithmNameEv The resulting tree looks like: typed name qualified name typed name qualified name name 'CryptoPP' name 'NullRNG' function type const this qualified name name 'NullRNG' name 'AlgorithmName' function type It seems to me that the const this applies to the AlgorithmName, and should be printed after its argument list. Instead it's printed as: CryptoPP::NullRNG()::NullRNG::AlgorithmName const() The old demangler did this too. This is presumably caused by the 'odd' qualified name whose leftmost part is a typed name. -- Summary: Another demangler problem with method cv-qualifiers Product: gcc Version: 3.4.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: ian at airs dot com ReportedBy: drow at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org GCC host triplet: i386-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13447
next reply other threads:[~2003-12-19 15:59 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-12-19 16:32 drow at gcc dot gnu dot org [this message] 2003-12-19 16:35 ` [Bug c++/13447] " ian at wasabisystems dot com 2003-12-19 16:37 ` drow at mvista dot com 2003-12-19 18:41 ` ian at wasabisystems dot com 2003-12-19 18:57 ` drow at mvista dot com 2003-12-19 19:18 ` ian at wasabisystems dot com 2003-12-19 19:28 ` giovannibajo at libero dot it 2003-12-19 19:29 ` drow at mvista dot com 2003-12-19 21:45 ` cvs-commit at gcc dot gnu dot org 2003-12-20 0:32 ` ian at airs dot com 2003-12-20 1:59 ` dhazeghi at yahoo dot com 2004-06-28 22:34 ` cvs-commit at gcc dot gnu dot org 2004-07-01 10:59 ` cvs-commit at gcc dot gnu dot org
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=20031219155953.13447.drow@gcc.gnu.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: linkBe 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).