Subject: Re: kern/13369: gcc inlines memcpy(3)
To: Oleg Polianski <Oleg.Polianski@clear.co.nz>
From: MINOURA Makoto <minoura@netbsd.org>
List: netbsd-bugs
Date: 07/05/2001 12:16:05
|> In <sa1ynwi8zw.fsf@simoom.clear.net.nz>
|> Oleg Polianski <Oleg.Polianski@clear.co.nz> wrote:
> There is a special option, `-fno-builtin', that prevents gcc from
> recognizing and inlining of well known functions like `memcpy', `memcmp' and
> some other (math) functions. Plese consult `info gcc' for more information.
I do not think disabling a particular optimization is a good
solution. What I wanted to say was just bcopy() should not
screw up with src/dst overlaps.
Of course in the long term it is nice to replace all bcopy()
calls with memcpy() or memmove() appropriately, since memcpy()
is a bit faster than memmove() and (correct) bcopy().
--
Minoura Makoto <minoura@netbsd.org>