[valgrind] [Bug 394227] [x86] False negative "uninitialised value" report due to not recognizing simd registers clear by pcmp*

https://bugs.kde.org/show_bug.cgi?id=394227 --- Comment #5 from n...@deditus.de --- Also related: https://bugs.kde.org/show_bug.cgi?id=398153 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 394227] [x86] False negative "uninitialised value" report due to not recognizing simd registers clear by pcmp*

https://bugs.kde.org/show_bug.cgi?id=394227 --- Comment #4 from n...@deditus.de --- The specific case of `pcmpeqw xmm0, xmm0` is claimed to be fixed in issue https://bugs.kde.org/show_bug.cgi?id=290006. Yet, there are still issues with valgrind on libjpeg-turbo (see

[valgrind] [Bug 394227] [x86] False negative "uninitialised value" report due to not recognizing simd registers clear by pcmp*

https://bugs.kde.org/show_bug.cgi?id=394227 n...@deditus.de changed: What|Removed |Added CC||n...@deditus.de -- You are receiving this

[valgrind] [Bug 394227] [x86] False negative "uninitialised value" report due to not recognizing simd registers clear by pcmp*

https://bugs.kde.org/show_bug.cgi?id=394227 --- Comment #3 from Julian Seward --- This is probably easy to fix, but we need a test case that shows the problem for all pcmpeq variants that you are interested in. Can you supply one? -- You are receiving this mail because: You are watching all

[valgrind] [Bug 394227] [x86] False negative "uninitialised value" report due to not recognizing simd registers clear by pcmp*

https://bugs.kde.org/show_bug.cgi?id=394227 ac...@free.fr changed: What|Removed |Added CC||ac...@free.fr --- Comment #2 from ac...@free.fr

[valgrind] [Bug 394227] [x86] False negative "uninitialised value" report due to not recognizing simd registers clear by pcmp*

https://bugs.kde.org/show_bug.cgi?id=394227 Philippe Waroquiers changed: What|Removed |Added CC|