minoura@netbsd.org (MINOURA Makoto) writes:

> >  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().

 Oops, looks like I missed some parts of your discussion it seemed to me that
 you're going to fix the code generating part of gcc. Sorry for
 misunderstanding.

-- 
        -- Oleg Polianski <Oleg.Polianski@clear.co.nz>