From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, mjw@redhat.com
Subject: Re: RFA: add .gdb_index documentation to gdb.texinfo
Date: Wed, 20 Apr 2011 15:42:00 -0000 [thread overview]
Message-ID: <83y6352ako.fsf@gnu.org> (raw)
In-Reply-To: <m3r58x2fd1.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> CC: Mark Wielaard <mjw@redhat.com>
> Date: Wed, 20 Apr 2011 07:59:22 -0600
>
> This patch moves the documentation from a comment in dwarf2read.c to the
> manual.
Thanks!
> +@node Index Section Format
> +@appendix .gdb_index section format
".gdb_index" should be in @code in the @appendix line.
> +@cindex .gdb_index section format
I would also add another @cindex entry, "index section format".
> +The section documents the index section that is created by @code{save
^^^^^^^^^^^
You probably meant "This section" here.
> +@code{offset_type}. Big endian machines must byte-swap the values
> +before using them. Exceptions to this rule are noted. The data is
^^
Two spaces, please.
> +A string in the constant pool is @samp{\0}-terminated.
I think "zero-terminated" is better.
> +The hash value for a table entry is computed by an applying an
^^
Remove that extra "an".
> +The step size used in the hash table is computed via
> +@code{((hash * 17) & (size - 1)) | 1}, where @samp{hash} is the hash
> +value, and @samp{size} is the size of the hash table.
It's unclear from the text when is this "step size" used. Perhaps say
a word or two about that.
> +The names of C@t{++} symbols in the hash table are canonicalized. We
> +don't currently have a simple description of the canonicalization
> +algorithm; if you intend to create new index sections, you must read
> +the code.
> +
> +A CU vector in the constant pool is a sequence of @code{offset_type}
> +values. The first value is the number of CU indices in the vector.
> +Each subsequent value is the index of a CU in the CU list. This
> +element in the hash table is used to indicate which CUs define the
> +symbol.
The text of this @item interleaves information about the hash table
proper with info about the constant pool, which is actually described
in the next @item. Perhaps it would be good to have all the info
about the constant pool in the next item of the enumerated list?
Thanks.
next prev parent reply other threads:[~2011-04-20 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 13:59 Tom Tromey
2011-04-20 15:42 ` Eli Zaretskii [this message]
2011-04-20 17:19 ` Tom Tromey
2011-04-20 17:35 ` 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=83y6352ako.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mjw@redhat.com \
--cc=tromey@redhat.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