Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: DJ Delorie <dj@redhat.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: Add crc32 function to libiberty
Date: Sat, 25 Jul 2009 06:16:00 -0000	[thread overview]
Message-ID: <m3k51xzjbq.fsf@google.com> (raw)
In-Reply-To: <200907242331.n6ONVqSl003646@greed.delorie.com> (DJ Delorie's message of "Fri\, 24 Jul 2009 19\:31\:52 -0400")

DJ Delorie <dj@redhat.com> writes:

> Please make sure any CRC routines added to libiberty document the
> polynomial they use.  Referencing a web site that may vanish at any
> time is too risky, despite how standard this polynomial happens to be
> at the moment.

I didn't reference the web site for the polynomial, just for background.
To be honest, I'm not sure what the polynomial is.  As the comments
explain, the algorithm I used is precisely taken from gdb, in remote.c,
and is intended to produce the same result.  Does anybody on the gdb
side know the polynomial or any other information?

Ian


  reply	other threads:[~2009-07-25  0:40 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 [this message]
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
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=m3k51xzjbq.fsf@google.com \
    --to=iant@google.com \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.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