Dear Scott Wood,
In message 20110524143749.0b508c66@schlenkerla.am.freescale.net you wrote:
Might want to pass -fno-delete-null-pointer-checks...
Thanks for pointing out.
As for memcpy/memmove, if in U-Boot it's to be legal to pass overlapping regions to memcpy(), why have separate implementations (not to mention bcopy...)?
Define "legal"? Legal as in "everything that is not explicitly forbidden"? Legal as in "any code that does not exwecute the HCF instruction"?
The man page says: "The memory areas should not overlap. Use memmove(3) if the memory areas do overlap." I have nothing to add here.
As for the different implementations: well, U-Boot imported tons of code from different sources, using different interfaces and library functions. Where needed, the missing library functions got added.
Cleanup patches are always welcome.
Best regards,
Wolfgang Denk