From: Ian Lance Taylor <iant@google.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org, dj@redhat.com
Subject: Re: Add crc32 function to libiberty
Date: Sat, 25 Jul 2009 07:16:00 -0000 [thread overview]
Message-ID: <m3fxclzj4o.fsf@google.com> (raw)
In-Reply-To: <6dc9ffc80907241723w18e945a5x6c665ec1780da6af@mail.gmail.com> (H. J. Lu's message of "Fri\, 24 Jul 2009 17\:23\:46 -0700")
"H.J. Lu" <hjl.tools@gmail.com> writes:
> On Fri, Jul 24, 2009 at 3:49 PM, Ian Lance Taylor<iant@google.com> wrote:
>> Some upcoming work in gold (by Sriraman Tallam) requires a CRC function.
>> I could add a CRC function to gold, but I think it makes sense to add it
>> to libiberty instead. This CRC function is a copy of the one in gdb,
>> except that the table of constants is precomputed. The gdb maintainers
>> may want to consider switching to this version--I don't think 1K of
>> read-only data space is all that much these days.
>
> Is that possible to use a compatible polynomia so that hardware
> crc32 in SSE4.2 can be used if available?
As the comments in the file explain, the algorithm is intended to
compute the precise CRC that gdb computes. That CRC could be hard to
change, as it is used in the remote protocol between gdb and stubs
running on remote targets.
I have no objection to having libiberty also provide an SSE 4.2
compatible polynomial if anybody wants to work on that.
Ian
next prev parent reply other threads:[~2009-07-25 0:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 23:39 Ian Lance Taylor
2009-07-24 23:55 ` DJ Delorie
2009-07-25 6:16 ` Ian Lance Taylor
2009-07-25 15:13 ` Eli Zaretskii
2009-07-25 20:48 ` Michael Snyder
2009-07-25 20:51 ` Michael Snyder
2009-07-25 22:09 ` Dave Korn
2009-07-26 19:12 ` Jeremy Bennett
2009-08-04 17:36 ` Ping: CRC32 documentation patch Jeremy Bennett
2009-08-04 18:20 ` Eli Zaretskii
2009-08-05 10:24 ` Jeremy Bennett
2009-08-05 17:47 ` Eli Zaretskii
2009-07-25 0:44 ` Add crc32 function to libiberty H.J. Lu
2009-07-25 7:16 ` Ian Lance Taylor [this message]
2009-07-26 12:30 ` Frank Ch. Eigler
2009-07-25 7:27 ` Eli Zaretskii
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=m3fxclzj4o.fsf@google.com \
--to=iant@google.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.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