https://bugs.kde.org/show_bug.cgi?id=387766
--- Comment #4 from Markus Trippelsdorf <octopl...@yandex.com> --- (In reply to Markus Trippelsdorf from comment #3) > (In reply to Ivo Raisr from comment #2) > > (In reply to Markus Trippelsdorf from comment #0) > > > Running gcc trunk under valgrind produces many false positives, e.g.: > > > > Please provide a simple standalone reproducer. For example, could a part of > > update_costs_from_copies() be isolated to reproduce the problem? > > > > There is also a patch for Valgrind which makes it to spend some extra time > > to accurately track definedness: > > https://bugs.kde.org/show_bug.cgi?id=387664 > > > > Please could you try to build Valgrind with this patch and then run it with > > --expensive-definedness-checks=yes (or --expensive-definedness-checks=auto). > > Your patch fixes the issue. Thanks. Actually no. Trunk is fine without any patch at all (and without --expensive-definedness-checks=yes). So it looks like the issue is already fixed. -- You are receiving this mail because: You are watching all bug changes.
