Steve Underwood schrieb:
That old thread seems to have faded away without conclusion. I will try
to do something about it. However, I am not sure what to do. The routine
which was posted in about the simplest we could use, so it is the
smallest. However, it is not efficient. Should I go for size or speed
(and consider speed affects power consumption - the faster code will be
more energy efficient :-) )?
i vote for these priorties:
1. code size
2. speed
developers rather complain about a programm not fitting in the CPU on
their desk than a battery that doesn't last that long. also, compilers
are often compared by generated code size ;-)
implementing a power efficient variant is always possible. (we could
provide a low power libc that can optionally be linked instead of the
normal one.)
a fast and not too large memcopy/memset could copy the start and end
separately using byte ops when odd, and copy the remaining data in
beween with word moves.
chris
