public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zackw at panix dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/41233] New: Templated conversion operator produces symbol name that won't demangle Date: Thu, 03 Sep 2009 00:21:00 -0000 [thread overview] Message-ID: <bug-41233-37@http.gcc.gnu.org/bugzilla/> (raw) This program class Source; class Dest; struct converter { converter(Source *s) {} template<class D> operator D*(); }; Dest* f(Source* s) { return converter(s); } when compiled by several different versions of g++ (I tried 4.3.4 and 4.4.1; the person who asked me to reduce the test case found the problem on OSX with some version of Apple-modified gcc 4.2), produces this symbol name for the conversion operator: _ZN9convertercvPT_I4DestEEv c++filt from binutils 2.19 will not demangle this symbol. I have not been able to figure out for certain whether this is an incorrect mangling, a demangler bug, or both. These variations demangle to close approximations of the right thing: _ZN9convertercvT_IN4DestEEEv -> converter::operator Dest<Dest>() _ZN9convertercvT_IPN4DestEEEv -> converter::operator Dest*<Dest*>() but _ZN9convertercvPT_IN4DestEEEv does not demangle, either. -- Summary: Templated conversion operator produces symbol name that won't demangle Product: gcc Version: 4.4.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: zackw at panix dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41233
next reply other threads:[~2009-09-03 0:21 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-09-03 0:21 zackw at panix dot com [this message] 2010-02-25 16:33 ` [Bug c++/41233] " jim at clkda dot com 2010-02-25 16:35 ` jim at clkda dot com 2010-02-25 20:02 ` jim at clkda dot com 2010-05-29 8:17 ` gcc at magfr dot user dot lysator dot liu dot se
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=bug-41233-37@http.gcc.gnu.org/bugzilla/ \ --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).