https://bugs.kde.org/show_bug.cgi?id=397313
--- Comment #4 from Axel <axel.huebl@plasma.ninja> --- Thanks, that's understandable. But since it's ok for a long double to only store its values in 80 bits, what shall we do about it? Should that specific case be suppressed by valgrind? Address/memory sanitizers seem to handle our snippets gracefully: clang -g -fsanitize=address main.c && ./a.out clang -g -fsanitize=memory main.c && ./a.out gcc -g -fsanitize=address main.c && ./a.out (all ok) clang -g main.c && valgrind --track-origins=yes ./a.out (this report) -- You are receiving this mail because: You are watching all bug changes.
