https://bugs.kde.org/show_bug.cgi?id=385409
--- Comment #50 from Andreas Arnez <ar...@linux.ibm.com> ---
Vadim, thanks for the reworks of VLL and VFENE. These help quite considerably,
and the false positives we've seen before are gone. Now I'm debugging an
internal error that seems related to the z13 patches, but not necessarily to
VLL and VFENE ("valgrind: the 'impossible' happened: LibVEX called
failure_exit()"). I'll let you know when I find out more about its cause.
In the meantime I noticed that we have another fundamental problem that comes
with GCC's inlined strlen: The last vector load (VL, or with length = VLL) may
read past an allocated buffer, causing an "invalid read". But of course
reading beyond the buffer is actually OK, as long as no page boundary is
crossed and the data beyond the buffer is ignored. I'm not sure how to get rid
of these false positives. Any advice?
--
You are receiving this mail because:
You are watching all bug changes.
