public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ccoutant at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/58591] New: GCC emits bad mangling for template function with a parameter pack Date: Tue, 01 Oct 2013 22:43:00 -0000 [thread overview] Message-ID: <bug-58591-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58591 Bug ID: 58591 Summary: GCC emits bad mangling for template function with a parameter pack Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ccoutant at gcc dot gnu.org Created attachment 30944 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30944&action=edit Reduced test case This is reduced from <bits/stl_construct.h>. Compiling the attached file with: $ g++ -S -std=c++11 mangle-test.cc Produces the following mangled name for the function Construct: _Z9ConstructI1AIiiEEvPT_DpOT0_ This cannot be demangled, because the T0_ reference at the end refers to a non-existent second template parameter. Removing the whole parameter pack from the mangling reveals a bogus mangling in the template parameter section: $ c++filt _Z9ConstructI1AIiiEEvPT_ void Construct<A<int, int> >(A<int, int>*) The type A is not a template -- the two ints together form the parameter pack that is the second template parameter.
next reply other threads:[~2013-10-01 22:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-01 22:43 ccoutant at gcc dot gnu.org [this message] 2013-10-01 22:49 ` [Bug c++/58591] " ccoutant at gcc dot gnu.org 2013-10-04 20:37 ` ccoutant at gcc dot gnu.org 2013-10-04 20:45 ` ccoutant at gcc dot gnu.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=bug-58591-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).