https://bugs.kde.org/show_bug.cgi?id=148543
--- Comment #5 from Tim Ruffing <pub...@timruffing.de> --- Sorry for posting again but I forgot to point out that this is a real problem in cases where compilers generate calls to memcpy() even if there's no explicit memcpy() call in the source, e.g., struct assignments. This happens for both GCC and Clang, see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32667 https://bugs.llvm.org/show_bug.cgi?id=11763 Of course it could be "fixed" there but it seems that at least Clang will move in the opposite direction and simply assume from libc that memcpy(x,x,n) is fine. So I think a suppression in Valgrind or at least a way to write one will be very useful and pragmatic. -- You are receiving this mail because: You are watching all bug changes.
