https://bugs.kde.org/show_bug.cgi?id=385409
--- Comment #43 from Vadim Barkov <vbr...@gmail.com> --- Generally speaking I think that warning in inline strlen is correct because the VFENE specification says: If ZS (zero search) flag is set, then each element in the second operand is compared for equality with zero. So, if we have this instruction: vfenezbs %v0, %v0, %v0 then all bytes of %v0 (second operand) are read in all cases (if the needed element found or not) So, if some bytes of %v0 are uninitialized for some reason, then the resulting condition code of VFENEZBS instruction is undefined. Anyway, the VFENE implementation is rewritten because in general case (when the second and third operand are different) the third operand is not read fully. What do you think about it? -- You are receiving this mail because: You are watching all bug changes.
