public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/28797] Problems with demangling (__cxa_demangle()) Date: Thu, 24 Aug 2006 06:20:00 -0000 [thread overview] Message-ID: <20060824062026.19875.qmail@sourceware.org> (raw) In-Reply-To: <bug-28797-13125@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from ian at airs dot com 2006-08-24 06:20 ------- Where did you get your list of symbol names and demangled strings? As Andrew has pointed out, there seem to be a few different issues here: different spacing, different qualifier order, different handling of floating point constants. It may well be appropriate to change gcc's demangler, but in my opinion these different issues should be handled as different problem reports. Other than those issues, I see one serious issue in this list: _Z1fM1AKiPKS1_, which the gcc demangler does not demangle, but you propose should be demangled as f(int const A::*, int const A::*const*). I have to agree with you that there appears to be something wrong with the demangler in this case. It is related to the long comment in d_pointer_to_member_type in cp-demangle.c. When I wrote that comment I believed that it was correct. However, it appears to now be incorrect. I haven't yet been able to track down the change to gcc which affected this. It is also possible that I was simply mistaken. -- ian at airs dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC|ian at gcc dot gnu dot org |ian at airs dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28797
next prev parent reply other threads:[~2006-08-24 6:20 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-08-22 3:57 [Bug libstdc++/28797] New: " kurkov at gorodok dot net 2006-08-22 5:21 ` [Bug other/28797] " pinskia at gcc dot gnu dot org 2006-08-22 5:26 ` pinskia at gcc dot gnu dot org 2006-08-22 5:52 ` kurkov at gorodok dot net 2006-08-24 6:20 ` ian at airs dot com [this message] 2006-08-25 8:50 ` kurkov at gorodok dot net 2006-08-26 18:54 ` ian at airs dot com 2006-08-26 19:04 ` ian at airs dot com 2006-08-27 21:43 ` ian at gcc dot gnu dot org 2006-08-27 21:44 ` ian at airs dot com 2007-01-10 19:40 ` pinskia 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=20060824062026.19875.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: 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).