public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/12019] memchr overshoots on Alpha
Date: Tue, 14 Sep 2010 18:37:00 -0000 [thread overview]
Message-ID: <20100914183653.8185.qmail@sourceware.org> (raw)
In-Reply-To: <20100914154213.12019.eblake@redhat.com>
------- Additional Comments From rth at gcc dot gnu dot org 2010-09-14 18:36 -------
Created an attachment (id=4980)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=4980&action=view)
Proposed alpha re-implementation
I came up with this re-write last year when the Debian people
pinged me about this problem. But I never heard back from the
guy that was supposed to test it on real hardware.
>From the ifdef alpha bit at the top you can see that I could
validate the algorithm from an x64 native host, but that isn't
really good enough.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=12019
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-09-14 18:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 15:42 [Bug libc/12019] New: " eblake at redhat dot com
2010-09-14 15:43 ` [Bug libc/12019] " eblake at redhat dot com
2010-09-14 16:15 ` drepper at gmail dot com
2010-09-14 18:30 ` eblake at redhat dot com
2010-09-14 18:32 ` vapier at gentoo dot org
2010-09-14 18:32 ` vapier at gentoo dot org
2010-09-14 18:35 ` mattst88 at gmail dot com
2010-09-14 18:37 ` rth at gcc dot gnu dot org [this message]
2010-09-14 21:31 ` eblake at redhat dot com
2010-09-15 7:42 ` schwab at linux-m68k dot org
2010-09-15 8:06 ` bonzini at gnu dot org
2010-09-15 8:23 ` schwab at linux-m68k dot org
2010-09-15 8:27 ` schwab at linux-m68k dot org
2010-09-15 13:42 ` eblake at redhat dot com
2010-09-15 16:04 ` rth at gcc dot gnu dot org
2010-09-15 16:28 ` eblake at redhat dot com
2010-09-15 16:44 ` eblake at redhat dot com
2010-09-15 16:45 ` eblake at redhat dot com
2010-09-15 17:48 ` rth at gcc dot gnu dot org
2010-09-22 22:47 ` eblake at redhat dot com
2010-09-23 10:48 ` mcree at orcon dot net dot nz
2010-09-23 15:09 ` rth at gcc dot gnu dot org
2010-09-26 8:33 ` mcree at orcon dot net dot nz
2010-09-26 18:14 ` rth at gcc dot gnu dot org
[not found] <bug-12019-131@http.sourceware.org/bugzilla/>
2014-06-30 8:03 ` fweimer at redhat dot com
2023-12-11 17:21 ` gabravier at gmail dot com
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=20100914183653.8185.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).