https://bugs.kde.org/show_bug.cgi?id=477992
--- Comment #2 from Barnabás Pőcze <po...@protonmail.com> --- I don't suggest turning off the overlap checks altogether. But maybe they could be relaxed to ignore exact overlaps, or there could be an option to not warn about the case where source = destination, or vica versa. > What about the Intel or AMD compilers? What about portability to MSVS? ICC seems to call `_intel_fast_memcpy`, and MSVC seems to call `memcpy`: https://gcc.godbolt.org/z/rbc7P81eo Now admittedly this is a tricky situation because I imagine ideally valgrind should somehow determine if the memcpy() call was generated by the compiler or not, and allow exact overlaps based on that. But I am not sure if that can even be determined (from DWARF?). -- You are receiving this mail because: You are watching all bug changes.
