Hmm my x86 is a bit rusty; have you got an actual test case that
triggers the warning?
It seems to be basically:
a) Do a bunch of individual character tests (32 bit at a time)
b) Do a bunch of tests of 64 bit words (pcmpeqd's) - i.e. 2 wchar's at a time
c) Get into an aligned loop doing 64 bytes at a time (using multiple
pcmpeqd's)
a) looks safe
Before (b) there is the code:
lea 32(%rdi), %rax
lea 16(%rdi), %rcx
and $-16, %rax
So I think that's aligning rax to a 16 byte boundary, so I'd hope what's
after it is safe
and Before (c) there is :
and $-0x40, %rax
.p2align 4
L(aligned_64_loop):
so again before going into that loop it's aligned to a 64byte boundary
So that feels ok with out having worked every path - although I'd kind
of expected valgrind to follow it.
If you've got the example and it shows exactly which instruction it's
moaning about it might be able to spot something.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1089722
Title:
wcslen reads beyond the end of the buffer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1089722/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
