From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] [gdb/symtab] Fix style issues in v9 .gdb_index section support
Date: Thu, 19 Oct 2023 13:55:48 -0300 [thread overview]
Message-ID: <87fs26tuuj.fsf@linaro.org> (raw)
In-Reply-To: <20231011153214.25769-1-tdevries@suse.de>
Hello Tom,
Tom de Vries <tdevries@suse.de> writes:
> @@ -1217,7 +1217,7 @@ write_shortcuts_table (cooked_index *table, data_buf& shortcuts,
> }
> }
>
> - shortcuts.append_uint (4, BFD_ENDIAN_LITTLE, dw_lang);
> + shortcuts.append_offset (dw_lang);
This is a functional change. Is it intentional? If so, it'd be better as
a separate patch.
> shortcuts.append_offset (main_name_offset);
> }
>
> diff --git a/gdb/dwarf2/read-gdb-index.c b/gdb/dwarf2/read-gdb-index.c
> index b96eaa96e23..34c5dfd5803 100644
> --- a/gdb/dwarf2/read-gdb-index.c
> +++ b/gdb/dwarf2/read-gdb-index.c
> @@ -777,10 +777,10 @@ static void
> set_main_name_from_gdb_index (dwarf2_per_objfile *per_objfile,
> mapped_gdb_index *index)
> {
> - const auto expected_size = 4 + sizeof (offset_type);
> + const auto expected_size = 2 * sizeof (offset_type);
This is also a functional change.
> if (index->shortcut_table.size () < expected_size)
> /* The data in the section is not present, is corrupted or is in a version
> - * we don't know about. Regardless, we can't make use of it. */
> + we don't know about. Regardless, we can't make use of it. */
One further style issue that could be fixed here is the lack of double
space after period.
> return;
>
> auto ptr = index->shortcut_table.data ();
> @@ -794,7 +794,7 @@ set_main_name_from_gdb_index (dwarf2_per_objfile *per_objfile,
> if (dw_lang == 0)
> {
> /* Don't bother if the language for the main symbol was not known or if
> - * there was no main symbol at all when the index was built. */
> + there was no main symbol at all when the index was built. */
> return;
Also here, double space after period is lacking.
> }
> ptr += 4;
> diff --git a/gdb/dwarf2/read.h b/gdb/dwarf2/read.h
> index 1d9432c5c11..c92474d8b9d 100644
> --- a/gdb/dwarf2/read.h
> +++ b/gdb/dwarf2/read.h
> @@ -246,11 +246,11 @@ struct dwarf2_per_cu_data
> std::vector <dwarf2_per_cu_data *> *imported_symtabs = nullptr;
>
> /* The original DW_LANG_* value of the CU, as provided to us by
> - * DW_AT_language. It is interesting to keep this value around in cases where
> - * we can't use the values from the language enum, as the mapping to them is
> - * lossy, and, while that is usually fine, things like the index have an
> - * understandable bias towards not exposing internal GDB structures to the
> - * outside world, and so prefer to use DWARF constants in their stead. */
> + DW_AT_language. It is interesting to keep this value around in cases where
> + we can't use the values from the language enum, as the mapping to them is
> + lossy, and, while that is usually fine, things like the index have an
> + understandable bias towards not exposing internal GDB structures to the
> + outside world, and so prefer to use DWARF constants in their stead. */
I think the lack of double space after period here are fixed in the
other patch you sent.
--
Thiago
next prev parent reply other threads:[~2023-10-19 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 15:32 Tom de Vries
2023-10-11 15:32 ` [PATCH 2/2] [gdb/symtab] Fix two style issues in gdb/dwarf2/index-write.c Tom de Vries
2023-10-17 20:07 ` Tom Tromey
2023-10-17 20:07 ` [PATCH 1/2] [gdb/symtab] Fix style issues in v9 .gdb_index section support Tom Tromey
2023-10-18 7:17 ` Tom de Vries
2023-10-19 0:01 ` Tom Tromey
2023-10-19 16:55 ` Thiago Jung Bauermann [this message]
2023-10-20 8:21 ` Tom de Vries
2023-10-20 16:50 ` Thiago Jung Bauermann
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=87fs26tuuj.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).