diff options
author | Julius Werner <jwerner@chromium.org> | 2020-08-21 15:20:02 -0700 |
---|---|---|
committer | Patrick Georgi <pgeorgi@google.com> | 2020-08-24 09:24:06 +0000 |
commit | ae096be00c3ada5acc6dfd601a1ad2bb36e234db (patch) | |
tree | 9fcb34c8453d386c88e147fb242b791f87de5696 /src/drivers/maxim | |
parent | 0c12abe4625e9bde9b31cbd9b1b9e2727bdee715 (diff) |
libpayload: memmove: Don't make expectations of architecture memcpy
default_memmove() calls memcpy() when (src > dst). This is safe for the
default_memcpy() implementation, but just calling memcpy() may invoke an
architecture-specific implementation. Architectures are free to
implement memcpy() however they want and may assume that buffers don't
overlap in either direction. So while this happens to work for all
current architecture implementations of memcpy(), it's safer not to rely
on that and only rely on the known implementation of default_memcpy()
for the forwards-overlapping case.
Signed-off-by: Julius Werner <jwerner@chromium.org>
Change-Id: I7ece4ce9e6622a36612bfade3deb62f351877789
Reviewed-on: https://review.coreboot.org/c/coreboot/+/44691
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/drivers/maxim')
0 files changed, 0 insertions, 0 deletions