[valgrind] [Bug 477992] compiler generated overlapping memcpy diagnosed

2023-12-15 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=477992 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[valgrind] [Bug 477992] compiler generated overlapping memcpy diagnosed

2023-12-14 Thread Sam James
https://bugs.kde.org/show_bug.cgi?id=477992 Sam James changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill |

[valgrind] [Bug 477992] compiler generated overlapping memcpy diagnosed

2023-12-14 Thread Sam James
https://bugs.kde.org/show_bug.cgi?id=477992 Sam James changed: What|Removed |Added See Also||https://gitlab.freedesktop. |

[valgrind] [Bug 477992] compiler generated overlapping memcpy diagnosed

2023-12-14 Thread Sam James
https://bugs.kde.org/show_bug.cgi?id=477992 Sam James changed: What|Removed |Added CC||s...@gentoo.org See Also|

[valgrind] [Bug 477992] compiler generated overlapping memcpy diagnosed

2023-12-04 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=477992 --- Comment #3 from Paul Floyd --- Debuginfo won't help with optimized builds. Sanitizers might be able to annotate code like this so that it gets ignored. In Valgrind there are just the two addresses and the size. There's no way to tell that the

[valgrind] [Bug 477992] compiler generated overlapping memcpy diagnosed

2023-12-03 Thread Barnabás Pőcze
https://bugs.kde.org/show_bug.cgi?id=477992 --- Comment #2 from Barnabás Pőcze --- 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

[valgrind] [Bug 477992] compiler generated overlapping memcpy diagnosed

2023-12-03 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=477992 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #1 from Paul Floyd