public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rafael.espindola at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/55170] New: incorrect mangling, should not include prefix Date: Thu, 01 Nov 2012 20:24:00 -0000 [thread overview] Message-ID: <bug-55170-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55170 Bug #: 55170 Summary: incorrect mangling, should not include prefix Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: rafael.espindola@gmail.com Given the testcase namespace mozilla { template<typename From> struct IsConvertible { static const bool value =true; }; template<bool B> struct EnableIf { typedef int Type; }; template <typename S> void Handle(S x, typename EnableIf<IsConvertible<S>::value>::Type dummy) { } template void Handle(int x, EnableIf<IsConvertible<int>::value>::Type dummy); } With current gcc trunk (193066) we get $ gcc -fabi-version=0 -c test.cpp -w $ nm test.o 0000000000000000 W _ZN7mozilla6HandleIiEEvT_NS_8EnableIfIXsrNS_13IsConvertibleIS1_EE5valueEE4TypeE And with clang $ ./build/bin/clang -c test.cpp $ nm test.o 0000000000000000 W _ZN7mozilla6HandleIiEEvT_NS_8EnableIfIXsr13IsConvertibleIS1_EE5valueEE4TypeE I initially thought the bug was in clang and reported llvm.org/pr14118, but John McCall says that "On cxx-abi-dev, I believe we decided that prefixes on unresolved-names should be mangled essentially as written".
next reply other threads:[~2012-11-01 20:24 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-01 20:24 rafael.espindola at gmail dot com [this message] 2012-11-01 20:29 ` [Bug c++/55170] " rafael.espindola at gmail dot com 2013-02-27 16:07 ` paolo.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=bug-55170-4@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).