From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Ian Lance Taylor <iant@google.com>,
Jim Blandy <jimb@red-bean.com>,
"dj@redhat.com" <dj@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Add crc32 function to libiberty
Date: Sat, 25 Jul 2009 22:09:00 -0000 [thread overview]
Message-ID: <4A6B76B6.2000504@gmail.com> (raw)
In-Reply-To: <4A6B6551.3050105@vmware.com>
Michael Snyder wrote:
> OK, google gives millions of hits for the crc const 0x04c11db7
> used by Ian's and my (remote.c) algorithm. I can't find my way
> to an original source, but apparently the algorithm was published
> as a part if IEEE 802.3 (ethernet), and is in very wide use
> (mpeg, png, v.42, posix cksum...)
>
> If you want to know the actual polynomial, this MIGHT be it
> (I guarantee nothing):
Take a read through the document at the URL that Ian quoted in the patch.
It is the most thoroughly comprehensive explanation you could ask for of the
nomenclature and variations of the crc algorithm.
cheers,
DaveK
next prev parent reply other threads:[~2009-07-25 21:05 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 [this message]
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=4A6B76B6.2000504@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=dj@redhat.com \
--cc=eliz@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=iant@google.com \
--cc=jimb@red-bean.com \
--cc=msnyder@vmware.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