From: Mark Wielaard <mark@klomp.org>
To: Gary Benson <gbenson@redhat.com>
Cc: gdb-patches@sourceware.org, Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: [RFA take 4] Allow setting breakpoints on inline functions (PR 10738)
Date: Tue, 14 Feb 2012 09:34:00 -0000 [thread overview]
Message-ID: <20120214093344.GA2439@toonder.wildebeest.org> (raw)
In-Reply-To: <20120213184700.GA31170@redhat.com>
On Mon, Feb 13, 2012 at 06:47:00PM +0000, Gary Benson wrote:
> This patch bumps the version number of the .gdb-index to 6, but
> it does not remove any of the backwards compatibility code which
> I would prefer to do as a separate patch.
> [...]
> @item
> -The version number, currently 5. Versions 1, 2 and 3 are obsolete.
> -Version 4 differs by its hashing function.
> +The version number, currently 6. Versions 1, 2, 3, 4 and 5 are
> +obsolete.
>
> @item
> The offset, from the start of the file, of the CU list.
> @@ -38786,18 +38778,9 @@ valid index for both a string and a CU vector.
> The hash value for a table entry is computed by applying an
> iterative hash function to the symbol's name. Starting with an
> initial value of @code{r = 0}, each (unsigned) character @samp{c} in
> -the string is incorporated into the hash using the formula depending on the
> -index version:
> -
> -@table @asis
> -@item Version 4
> -The formula is @code{r = r * 67 + c - 113}.
> -
> -@item Version 5
> -The formula is @code{r = r * 67 + tolower (c) - 113}.
> -@end table
> -
> -The terminating @samp{\0} is not incorporated into the hash.
> +the string is incorporated into the hash using the formula
> +@code{r = r * 67 + tolower (c) - 113}. The terminating @samp{\0} is
> +not incorporated into the hash.
>
> The step size used in the hash table is computed via
> @code{((hash * 17) & (size - 1)) | 1}, where @samp{hash} is the hash
I think you should keep the historical information about older
versions and add precisely which symbols weren't included with
version 5 that are now included with version 6 in the documentation
of the gdb index format. That will be helpful for other producers
and consumers of the .gdb_index section (elfutils/binutils readelf,
gold --gdb-index option).
Thanks,
Mark
next prev parent reply other threads:[~2012-02-14 9:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 18:47 Gary Benson
2012-02-14 1:39 ` Doug Evans
2012-02-14 9:02 ` Gary Benson
2012-02-15 8:05 ` Doug Evans
2012-02-15 12:17 ` Gary Benson
2012-02-15 20:14 ` Doug Evans
2012-02-16 10:41 ` Gary Benson
2012-02-17 22:42 ` Doug Evans
2012-02-21 16:32 ` Gary Benson
2012-02-14 9:34 ` Mark Wielaard [this message]
2012-02-14 9:38 ` Jan Kratochvil
2012-02-14 9:48 ` Mark Wielaard
2012-02-14 10:51 ` Gary Benson
2012-02-14 18:04 ` 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=20120214093344.GA2439@toonder.wildebeest.org \
--to=mark@klomp.org \
--cc=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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