* Obscure name mangling issue with gcc 2.95.2
@ 2001-12-31 23:21 Middleton, Ted
0 siblings, 0 replies; only message in thread
From: Middleton, Ted @ 2001-12-31 23:21 UTC (permalink / raw)
To: 'gcc-help@gcc.gnu.org'
Could someone clarify for me when gcc will generate mangled names with the N
parameter key and when it will use the T parameter key? gcc is
intermittently using both and it's causing linking problems, both within my
project and with a library I'm linking to. For example, right now, I'm
trying to link with this function
void MyClass::GetBackBufferInfo(int *addr, int *psm, int *width)
and the symbol that ends up in my code is this:
U GetBackBufferInfo__Q211MyNamespace7MyClassPiN21
but the library I compiled (same compiler) has this:
0000000000004108 T GetBackBufferInfo__Q211MyNamespace7MyClassPiT1T1
Does anyone have any insight that they could offer?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2002-01-01 1:10 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-12-31 23:21 Obscure name mangling issue with gcc 2.95.2 Middleton, Ted
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).