Bug#728953: strtod: Valgrind reports invalid read when first char is 'n' (in the x86_64 version)

[Aurelien Jarno <aurelien@aurel32.net>]

reassign 728953 valgrind
thanks

On Thu, Nov 07, 2013 at 11:07:00AM +0100, Boris D. Carlsson wrote:
> Package: libc6
> Version: 2.13-38
> Severity: minor
> 
> When strtod receives a string starting with 'n', it will read 16
> bytes regardless of the actual length of the string sent.
> 

strtod calls strncasecmp which uses SSE code to compare 16 bytes at a
time. The code ensures that it will not cross cache line, and thus not
page size, so this is fine as long at it discards any data resulting
from comparison after the end of the string, which it does.

There is therefore no issue with this code in libc, I am reassigning the
bug to valgrind where some suppression files should be updated.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net