memcpy performance (fwd)

[Jonathan Larmour]

Joel Sherrill wrote:
>Eric Norum wrote:
> /shareNeXT/OS4.2/RTEMS/src/tools-970904/build-m68k-tools/gcc/xgcc
> -B/shareNeXT/OS4.2/RTEMS/src/tools-970904/build-m68k-tools/gcc/
> -idirafter
> /shareNeXT/OS4.2/RTEMS/src/tools-970904/build-m68k-tools/m68k-rtems/newlib/targ-include
> -idirafter
> /shareNeXT/OS4.2/RTEMS/src/tools-970904/src/newlib/libc/include
> -nostdinc -O2 -g -pipe  -m68332  -O2 -DHAVE_GETTIMEOFDAY
> -DMALLOC_PROVIDED -DEXIT_PROVIDED -DMISSING_SYSCALL_NAMES
> -DSIGNAL_PROVIDED -DREENTRANT_SYSCALLS_PROVIDED -fno-builtin
> -I/shareNeXT/OS4.2/RTEMS/src/tools-970904/build-m68k-tools/m68k-rtems/newlib/./targ-include
> -I/shareNeXT/OS4.2/RTEMS/src/tools-970904/src/newlib/./libc/include
> -c ../../../../../../src/newlib/libc/string/memcpy.c

The -fno-builtin would probably explain why the gcc version isn't used.
It looks very deliberate though! He could try removing it, unless he
knows why it should be there, or wait until someone else with more
experience of this particular port can explain!

HTH,

Jonathan L.