From: "John S. Fine" <johnfine AT erols DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: NASM "name mangling"
Date: Tue, 17 Nov 1998 15:14:38 -0500
Lines: 19
Message-ID: <3651D92E.6BFF@erols.com>
References: <72ifbf$4qm$1 AT news DOT metronet DOT de> <36516beb DOT 0 AT 139 DOT 134 DOT 5 DOT 33>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: Assi/KFj/MmEXDeW0s9KqVJ54E/fdWtb6N+p2vXTD1c=
X-Complaints-To: abuse AT rcn DOT com
NNTP-Posting-Date: 17 Nov 1998 20:15:30 GMT
X-Mailer:  Mozilla 3.01 (Win95; U)
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Johan Venter (aka sphinX) wrote:

> [GLOBAL _blit_FPUiPUiUi]
> 
> and when i compiled my source and used this function, gcc returned 'undefined reference'.
. . .
> It seemed that either gcc or nasm didn't like that long function name,

   I would like to check whether that is a NASM bug (and if not,
see what the problem is).  I am too busy/lazy to install the C++
portion of djgpp (I use djgpp only for C).

   If you send me a .o file for C++ that requests the failing
mangled name, plus a NASM .asm file that tries to define it,
I think I can determine where the problem is and fix NASM if
the problem is there.
-- 
http://www.erols.com/johnfine/
http://www.geocities.com/SiliconValley/Peaks/8600/