[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: broken memchr
From: |
Simon Josefsson |
Subject: |
Re: broken memchr |
Date: |
Mon, 08 Jun 2009 14:17:54 +0200 |
User-agent: |
Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.94 (gnu/linux) |
Eric Blake <address@hidden> writes:
> According to Simon Josefsson on 5/26/2009 10:24 AM:
>> My gnulib autobuilder is a x86_64 system (running Ubuntu 8.04 LTS), so
>> if the test starts to fail, it will show up here in a few hours:
>>
>> http://autobuild.josefsson.org/gnulib/#000-gnulib-simple-gaggia
>
> The updated test-memchr is passing on your autobuilder; which version of
> glibc do you have on that machine?
Version 2.7. It is an Ubuntu 8.04 LTS (virtual) machine.
> We know the broken memchr on x86_64 is in 2.10 but not current glibc
> (which will become 2.11), and based on the glibc release notes, I
> don't think the bug was present in 2.9 either:
>
> | Version 2.10
> ...
> | * Faster strlen, strchr, strchrnul, strrchr, memchr, and rawmemchr for
> x86-64.
> | Implemented by Ulrich Drepper.
>
> I guess I'd like to see a failure report for test-memchr in the wild
> before worrying about replacing that function in gnulib, although I'm
> fairly confident that we should be able to find one. The broken alpha
> version may have been around longer, and I'm not sure whether it is fixed
> yet, but alpha seems to be a less popular architecture.
I agree it would be best to wait for a real failure report. I wonder if
glibc 2.10 has been widely deployed?
/Simon