https://bugs.kde.org/show_bug.cgi?id=492210
--- Comment #8 from Paul Floyd <pjfl...@wanadoo.fr> --- (In reply to Alexander Monakov from comment #7) > (In reply to Paul Floyd from comment #6) > > It looks like these have been added as needed, not systematically to cover > > all cases. > > In GCC we cannot leave compiling-under-valgrind broken until a release of > Valgrind with the fix for a false positive appears. We apply a workaround > (in this case, initializing a few bytes more) and move on. As far as > vectorized code in libcpp is concerned, a fix for this particular case is > not needed anymore. If all false positives are fixed in this manner — > covering just one case on just one architecture, when the original project > already worked around it — all it may amount to is accumulation of dead > weight. This item is my next priority. I'd like to be sure of getting it into 3.24. -- You are receiving this mail because: You are watching all bug changes.
