public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "uttamp at us dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/16240] [3.4/3.5 ABI Regression] g++ generates incorrect mangled name Date: Fri, 29 Jul 2005 18:31:00 -0000 [thread overview] Message-ID: <20050729181614.29989.qmail@sourceware.org> (raw) In-Reply-To: <20040628024250.16240.mckelvey@maskull.com> ------- Additional Comments From uttamp at us dot ibm dot com 2005-07-29 18:16 ------- I belive, till g++ 3.3.4, the mangled string used have that '_' as hown by following example, template<class T> struct S { S(int i=0); }; template<S<int> &s> void f13(); extern S<int> s13; int main(void) { f13<s13>(); return 0; } With nm, I get U __gxx_personality_v0 00000000 T main U _Z3f13IXL_Z3s13EEEvv Which I believe is the default and correct behavior. But with g++ > 3.4 (which doesn't support abi-version=3) by default produces mangled string as U __gxx_personality_v0 00000000 T main U _Z3f13ILZ3s13EEvv And with g++ > 3.5.x user has to specify -fabi-version=3 as specified by Mark, to get the correct string. So there is a binary compatibility problem between object code created by older g++ version < 3.3.4 and later version till g++ version 3.5. Do you see my dilemma? Or am I still missing something very basic here? Sorry for any/all repetition over this subject. I would really appreciate the reply for better understanding and clarification of this issue. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16240
next prev parent reply other threads:[~2005-07-29 18:16 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-06-28 2:46 [Bug c++/16240] New: Seg Fault in collect2 mckelvey at maskull dot com 2004-06-28 3:24 ` [Bug c++/16240] " mckelvey at maskull dot com 2004-06-28 5:17 ` [Bug driver/16240] " pinskia at gcc dot gnu dot org 2004-06-28 7:21 ` pinskia at gcc dot gnu dot org 2004-06-28 7:28 ` [Bug other/16240] [3.4/3.5 Regression] Seg Fault in collect2 (caused by C++ demangling) pinskia at gcc dot gnu dot org 2004-06-28 15:30 ` cvs-commit at gcc dot gnu dot org 2004-06-28 15:39 ` ian at wasabisystems dot com 2004-06-28 16:08 ` [Bug c++/16240] [3.4/3.5 Regression] g++ generates incorrect mangled name ian at wasabisystems dot com 2004-06-28 17:45 ` giovannibajo at libero dot it 2004-07-01 17:23 ` [Bug c++/16240] [3.4/3.5 ABI " bkoz at gcc dot gnu dot org 2004-07-02 23:56 ` cvs-commit at gcc dot gnu dot org 2004-07-02 23:58 ` mmitchel at gcc dot gnu dot org 2004-09-05 3:27 ` jbuck at gcc dot gnu dot org 2005-01-31 22:12 ` pinskia at gcc dot gnu dot org 2005-02-28 15:17 ` cvs-commit at gcc dot gnu dot org 2005-07-27 22:56 ` uttamp at us dot ibm dot com 2005-07-27 23:09 ` ian at airs dot com 2005-07-28 18:29 ` uttamp at us dot ibm dot com 2005-07-28 22:56 ` ian at airs dot com 2005-07-29 18:31 ` uttamp at us dot ibm dot com [this message] 2005-07-29 23:24 ` ian at airs dot com [not found] <bug-16240-6183@http.gcc.gnu.org/bugzilla/> 2009-02-16 22:41 ` jakub 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=20050729181614.29989.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).