Re: [PATCH] kdb: use memmove instead of overlapping memcpy

2018-02-02 Thread Jason Wessel
On 02/02/2018 08:59 AM, Arnd Bergmann wrote: gcc discovered that the memcpy() arguments in kdbnearsym() overlap, so we should really use memmove(), which is defined to handle that correctly: In function 'memcpy', inlined from 'kdbnearsym' at

Re: [PATCH] kdb: use memmove instead of overlapping memcpy

2018-02-02 Thread Jason Wessel
On 02/02/2018 08:59 AM, Arnd Bergmann wrote: gcc discovered that the memcpy() arguments in kdbnearsym() overlap, so we should really use memmove(), which is defined to handle that correctly: In function 'memcpy', inlined from 'kdbnearsym' at

[PATCH] kdb: use memmove instead of overlapping memcpy

2018-02-02 Thread Arnd Bergmann
gcc discovered that the memcpy() arguments in kdbnearsym() overlap, so we should really use memmove(), which is defined to handle that correctly: In function 'memcpy', inlined from 'kdbnearsym' at /git/arm-soc/kernel/debug/kdb/kdb_support.c:132:4: /git/arm-soc/include/linux/string.h:353:9:

[PATCH] kdb: use memmove instead of overlapping memcpy

2018-02-02 Thread Arnd Bergmann
gcc discovered that the memcpy() arguments in kdbnearsym() overlap, so we should really use memmove(), which is defined to handle that correctly: In function 'memcpy', inlined from 'kdbnearsym' at /git/arm-soc/kernel/debug/kdb/kdb_support.c:132:4: /git/arm-soc/include/linux/string.h:353:9: