This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: [patch] More Arm EABI support routines
On Thursday 01 September 2005 14:17, Richard Earnshaw wrote:
> On Thu, 2005-09-01 at 14:07, Paul Brook wrote:
> > > > 2005-08-31 Paul Brook <paul@codesourcery.com>
> > > >
> > > > * libc/sys/arm/Makefile.am (lib_a_SOURCES): Add aeabi_memclr.c,
> > > > aeabi_memcpy.c, aeabi_memmove.c and aeabi_memset.c.
> > > > * libc/sys/arm/Makefile.in: Regenerate.
> > > > * libc/sys/arm/aeabi.h: New file.
> > > > * libc/sys/arm/aeabi_memclr.c: New file.
> > > > * libc/sys/arm/aeabi_memcpy.c: New file.
> > > > * libc/sys/arm/aeabi_memmove.c: New file.
> > > > * libc/sys/arm/aeabi_memset.c: New file.
> > >
> > > I'm in two minds about this. Part of me thinks that this should be in
> > > libgcc rather than newlib, since these are documented as part of the
> > > standard run-time support for the compiler.
> >
> > My reason for putting them in libc was that they're then in the same
> > place as the underlying mem* routines.
>
> But the whole point of these entry points is that they can be more
> efficient than the mem* routines. So long-term we really don't want to
> implement them this way.
Maybe. I was also thinking that the the C library is more likely to know about
target specific properties (size/speed preference, coprocessor support/custom
insns, etc) than libgcc.
Paul