From: Eli Zaretskii <eliz@gnu.org>
To: jeremy.bennett@embecosm.com
Cc: gdb-patches@sourceware.org
Subject: Re: Ping: CRC32 documentation patch
Date: Tue, 04 Aug 2009 18:20:00 -0000 [thread overview]
Message-ID: <83ocqvo2z1.fsf@gnu.org> (raw)
In-Reply-To: <1249407367.3284.80.camel@thomas>
> From: Jeremy Bennett <jeremy.bennett@embecosm.com>
> Date: Tue, 04 Aug 2009 18:36:07 +0100
>
> This patch clarifies how CRC is calculated in the GDB manual. I think it
> probably got lost in the rest of the discussion of CRC.
Yes, sorry.
> Any comments?
Some.
> +The CRC used in @code{.gnu_debuglink} is the CRC-32 defined in
> +IEEE 802.3 using the polynomial @math{x^{32} + x^{26} + x^{23} + x^{22}
> ++ x^{16} + x^{12} +x^{11} + x^{10} + x^8 + x^7 + x^5 + x^4 + x^2 + x +
> +1}. The function is computed byte at a time, taking the least
Would the polynomial look better, both in print and in on-line
versions of the manual, if you put it into a @quotation or a @display,
and break it into separate lines manually? I fear that leaving the
line-breaking job to makeinfo or even TeX could produce ugly results
beyond our control.
> +significant bit of each byte first. The initial pattern
> +@code{0xffffffff} is used, to ensure leading zeros affect the CRC and
> +the final result is inverted to ensure trailing zeros also affect the
> +CRC.
Please leave two spaces between sentences, not one (here and elsewhere
in the patch).
> +For a complete explanation the code for the function used in
> +@code{.gnu_debuglink} is given here.
I suggest to reword like this (avoiding passive tense):
To complete the description, we show below the code of the function
which produces the CRC used in @code{.gnu_debuglink}.
Okay with these corrections.
Thanks.
next prev parent reply other threads:[~2009-08-04 18:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 23:39 Add crc32 function to libiberty 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 [this message]
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=83ocqvo2z1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jeremy.bennett@embecosm.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