From: Michael Cree <mcree@orcon.net.nz>
To: debian-alpha@lists.debian.org
Cc: 521737@bugs.debian.org, linux-alpha@vger.kernel.org
Subject: Re: current state of sid (unstable)
Date: Mon, 27 Sep 2010 19:53:06 +1300 [thread overview]
Message-ID: <4CA03F52.8010203@orcon.net.nz> (raw)
In-Reply-To: <4C973504.3020602@orcon.net.nz>
On 20/09/10 22:18, Michael Cree wrote:
> On 04/08/10 09:35, Michael Cree wrote:
>> On 4/08/2010, at 1:48 AM, Bob Tracy wrote:
>>> (5) Some long-standing compiler and libc issues have been fixed
>>> upstream and in Debian, but recently, a build of libc in Debian
>>> Unstable failed.
>>
>> I see the memchr seg fault bug (521737) is still open. I have a hunch
>> that it may be a false-positive,
>
> Darn, it's a true-positive.
A new version of memchr is now upstream in the glibc ports repository
(many thanks to RTH). In addition to fixing the seg fault it is more
than twice as fast as the old version when searching through large
memory buffers.
Cheers
Michael.
prev parent reply other threads:[~2010-09-27 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100803134859.GA9030@gherkin.frus.com>
[not found] ` <9AF94B53-DBAB-456E-B7FC-1E503375EB94@orcon.net.nz>
2010-09-20 10:18 ` current state of sid (unstable) Michael Cree
2010-09-27 6:53 ` Michael Cree [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CA03F52.8010203@orcon.net.nz \
--to=mcree@orcon.net.nz \
--cc=521737@bugs.debian.org \
--cc=debian-alpha@lists.debian.org \
--cc=linux-alpha@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).