From: Eli Zaretskii <eliz@gnu.org>
To: Ian Lance Taylor <iant@google.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:27:00 -0000 [thread overview]
Message-ID: <83hbx144hh.fsf@gnu.org> (raw)
In-Reply-To: <m363dh1yub.fsf@google.com>
> Cc: gdb-patches@sourceware.org, dj@redhat.com
> From: Ian Lance Taylor <iant@google.com>
> Date: Fri, 24 Jul 2009 15:49:00 -0700
I have a couple of comments about the documentation:
> +@deftypefn Extension unsigned int crc32 (const unsigned char *@var{buf}, int @var{len}, unsigned int @var{init})
> +
> +Compute the 32-bit CRC of @var{buf} which has length @var{len}. The
^^^^^^^^^^^^^^^^^^^^^^^^^^
A minor stylistic comment: perhaps "whose length is @var{len}" is better.
> +protocol for the @samp{qCRC} command. In order to get the same
> +results as gdb for a block of data, you must pass the first CRC
> +parameter as @code{0xffffffff}.
By "first CRC parameter", do you mean @var{init}? If so, I suggest to
say that explicitly.
Finally, perhaps tell what the "CRC" acronym stands for, first time
you use it in the text.
Thanks.
prev parent reply other threads:[~2009-07-25 7:16 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
2009-07-26 12:30 ` Frank Ch. Eigler
2009-07-25 7:27 ` Eli Zaretskii [this message]
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=83hbx144hh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=iant@google.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