From: Paul Shirley <Paul AT no DOT spam DOT please>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: inline asm ("g" or "a" for input... which is faster?) and  memory.h
Date: Tue, 8 Jul 1997 22:48:44 +0100
Organization: wot? me?
Distribution: world
Message-ID: <$5h6dKA8WrwzEwB4@foobar.co.uk>
References: <199707081711 DOT KAA26916 AT adit DOT ap DOT net>
Reply-To: Paul Shirley <Paul AT chocolat DOT obvious DOT fake DOT foobar DOT co DOT uk>
NNTP-Posting-Host: chocolat.foobar.co.uk
Mime-Version: 1.0
Lines: 15
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

In article <199707081711 DOT KAA26916 AT adit DOT ap DOT net>, Nate Eldredge
<eldredge AT ap DOT net> writes
>That bothers me slightly. It seems that certain functions such as strcpy,
>memset, etc, are magically known about by the compiler (it refers to them as
>builtin functions). This means I can't put a strcpy of my own in the program
>unless it goes in the same source file; otherwise GCC will inline its own.

Just use the -fno-builtin option to stop this.

(Since I've never managed to catch gcc actually doing this for me you
may notice no difference of course ;)

---
Visit www.dukepsx.com: see what I do all day.
Paul Shirley: my email address is 'obvious'ly anti-spammed