From:	dyoung AT vviuh221 DOT vvi DOT com (David Young)
Subject:	linking gcc & vc++ object files
1 Aug 1998 17:52:56 -0700 :
Message-ID:	<9808011437.AA01661.cygnus.gnu-win32@vviuh221.vvi.com>
Reply-To:	dyoung AT vviuh221 DOT vvi DOT com
To:	gnu-win32 AT cygnus DOT com

gnu-win32:

We are linking object files generated by gcc and object files  
generated by vc++ on Windows-NT. In order to get object files  
generated by gcc to link with object files generated by VC++ we have  
to append a "@n" suffix (n seems to be always a multiple of 4) to the  
function names (in the gcc related source files) whos object  
definition is in the files generated by VC++. That's because the VC++  
generates function symbols in object files with a "@n" suffix. Note,  
this has nothing to do with C++ name mangling, all function  
definitions are wrapped in extern "C" {} ; this is an ANSI-C related  
issue.

QUESTION: What is the "@n" all about?

From the list archives, I see this question was asked on this mail  
list before, but the responses were incongruent to say the least.

Your response is very welcome.
Please cc:: your response to dyoung AT vvi DOT com as I do not want to miss  
any input regarding this subject.

Thanks A Bunch!

David Young; vvi-dcs
dyoung AT vvi DOT com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -