Article View: gnu.gcc.help
Article #53222Re: gcc-2.0 name mangling
From: Christos Zoulas
Date: Fri, 06 Mar 1992 02:05
Date: Fri, 06 Mar 1992 02:05
27 lines
1590 bytes
1590 bytes
In article <TOMW.92Mar4123856@latchup.ucsb.edu> tomw@bears.ece.ucsb.edu writes: >In article <A33092@AC.maus.de>, Marc_Van-Woerkom@ac.maus.de (Marc Van-Woerkom) writes: > >>te> My questions are: why does it do this? Can I do anything to make them >>te> work correctly together? > >> Name mangling is different on different compilers! (No bug - a fact of life) > >Huh? This seems idiotic to me. That means I can't use C++ libs >compiled with a different compiler? I'm outraged! C doesn't have these >kinds of problems. > >> Try to use the extern "C" statements. > >That's really horrible. I'd have to find out the mangled names, and use >those? Ick. On the brighter side, I fixed GDB to understand cfront mangled names. My version of cfront mangles templates by appending __pt__ to the class names, and then the mangled types inside the <..>. Can someone with access to cfront 3.0 tell me how it is done there? Please don't ask me for patches yet, I am still testing it. Thanks, christos
Technical Details
Message-ID:
<1992Mar6.020554.22495@bond>Path:
arc1-ca.pugleaf.net!sparky!uunet!think.com!yale.edu!cmcl2!bond!christosReferences:
<A33777@HB.maus.de> <A33092@AC.maus.de> <TOMW.92Mar4123856@latchup.ucsb.edu>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11318c,d442a3a97625629c X-Google-Attributes: gid11318c,public X-Google-ArrivalTime: 1992-03-07 07:15:00 PST Newsgroups: gnu.gcc.help Path: arc1-ca.pugleaf.net!sparky!uunet!think.com!yale.edu!cmcl2!bond!christos From: bond!christos@nyu.edu (Christos Zoulas) Subject: Re: gcc-2.0 name mangling Organization: D. E. Shaw & Co. Date: Fri, 6 Mar 1992 02:05:54 GMT Message-ID: <1992Mar6.020554.22495@bond> References: <A33777@HB.maus.de> <A33092@AC.maus.de> <TOMW.92Mar4123856@latchup.ucsb.edu> Sender: nyu.edu!bond!news