public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: catherin@ca.ibm.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/8964: [3.3 regression] [ABI] different mangling of names Date: Mon, 16 Dec 2002 13:10:00 -0000 [thread overview] Message-ID: <20021216211008.13084.qmail@sources.redhat.com> (raw) Old Synopsis: 2 different templates mangled with the same name New Synopsis: [3.3 regression] [ABI] different mangling of names State-Changed-From-To: closed->analyzed State-Changed-By: bangerth State-Changed-When: Mon Dec 16 13:10:07 2002 State-Changed-Why: This little code --------------------------- template < class T,int I > struct A { typedef int X; }; template<class T> struct A<T,3> { typedef char X; }; template <template <class B,int I> class XX> void foo(typename XX<int,3>::X a){} int main() { foo<A>('x'); } ------------------------------- yields different mangled names with 3.2 and 3.3, which is an ABI change that should probably not be there unless guarded by -fabi-version: tmp/g> /home/bangerth/bin/gcc-3.2.2-pre/bin/c++ -c x.cc tmp/g> nm x.o | grep foo 00000000 W _Z3fooI1AEvN2XX1XE tmp/g> nm x.o | /home/bangerth/bin/gcc-3.2/bin/c++filt | grep foo 00000000 W void foo<A>(XX::X) tmp/g> /home/bangerth/bin/gcc-3.3-pre/bin/c++ -c x.cc tmp/g> nm x.o | grep foo 00000000 W _Z3fooI1AEvN2XXIiLi3EE1XE tmp/g> nm x.o | /home/bangerth/bin/gcc-3.2/bin/c++filt | grep foo 00000000 W void foo<A>(XX<int, (int)3>::X) http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8964
next reply other threads:[~2002-12-16 21:10 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-16 13:10 bangerth [this message] 2002-12-23 9:46 Janis Johnson
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=20021216211008.13084.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=catherin@ca.ibm.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).