From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [pushed] Reindent recursive_dump_type
Date: Fri, 4 Aug 2023 13:58:29 -0600 [thread overview]
Message-ID: <20230804195829.4128784-1-tromey@adacore.com> (raw)
I noticed that a 'switch' in recursive_dump_type was incorrect
indented. This patch fixes the problem. Tested by rebuilding.
---
gdb/gdbtypes.c | 66 +++++++++++++++++++++++++-------------------------
1 file changed, 33 insertions(+), 33 deletions(-)
diff --git a/gdb/gdbtypes.c b/gdb/gdbtypes.c
index c5272979cb9..d7db7beb554 100644
--- a/gdb/gdbtypes.c
+++ b/gdb/gdbtypes.c
@@ -5391,44 +5391,44 @@ recursive_dump_type (struct type *type, int spaces)
switch (TYPE_SPECIFIC_FIELD (type))
{
- case TYPE_SPECIFIC_CPLUS_STUFF:
- gdb_printf ("%*scplus_stuff %s\n", spaces, "",
- host_address_to_string (TYPE_CPLUS_SPECIFIC (type)));
- print_cplus_stuff (type, spaces);
- break;
+ case TYPE_SPECIFIC_CPLUS_STUFF:
+ gdb_printf ("%*scplus_stuff %s\n", spaces, "",
+ host_address_to_string (TYPE_CPLUS_SPECIFIC (type)));
+ print_cplus_stuff (type, spaces);
+ break;
- case TYPE_SPECIFIC_GNAT_STUFF:
- gdb_printf ("%*sgnat_stuff %s\n", spaces, "",
- host_address_to_string (TYPE_GNAT_SPECIFIC (type)));
- print_gnat_stuff (type, spaces);
- break;
+ case TYPE_SPECIFIC_GNAT_STUFF:
+ gdb_printf ("%*sgnat_stuff %s\n", spaces, "",
+ host_address_to_string (TYPE_GNAT_SPECIFIC (type)));
+ print_gnat_stuff (type, spaces);
+ break;
- case TYPE_SPECIFIC_FLOATFORMAT:
- gdb_printf ("%*sfloatformat ", spaces, "");
- if (TYPE_FLOATFORMAT (type) == NULL
- || TYPE_FLOATFORMAT (type)->name == NULL)
- gdb_puts ("(null)");
- else
- gdb_puts (TYPE_FLOATFORMAT (type)->name);
- gdb_puts ("\n");
- break;
+ case TYPE_SPECIFIC_FLOATFORMAT:
+ gdb_printf ("%*sfloatformat ", spaces, "");
+ if (TYPE_FLOATFORMAT (type) == NULL
+ || TYPE_FLOATFORMAT (type)->name == NULL)
+ gdb_puts ("(null)");
+ else
+ gdb_puts (TYPE_FLOATFORMAT (type)->name);
+ gdb_puts ("\n");
+ break;
- case TYPE_SPECIFIC_FUNC:
- gdb_printf ("%*scalling_convention %d\n", spaces, "",
- TYPE_CALLING_CONVENTION (type));
- /* tail_call_list is not printed. */
- break;
+ case TYPE_SPECIFIC_FUNC:
+ gdb_printf ("%*scalling_convention %d\n", spaces, "",
+ TYPE_CALLING_CONVENTION (type));
+ /* tail_call_list is not printed. */
+ break;
- case TYPE_SPECIFIC_SELF_TYPE:
- gdb_printf ("%*sself_type %s\n", spaces, "",
- host_address_to_string (TYPE_SELF_TYPE (type)));
- break;
+ case TYPE_SPECIFIC_SELF_TYPE:
+ gdb_printf ("%*sself_type %s\n", spaces, "",
+ host_address_to_string (TYPE_SELF_TYPE (type)));
+ break;
- case TYPE_SPECIFIC_FIXED_POINT:
- gdb_printf ("%*sfixed_point_info ", spaces, "");
- print_fixed_point_type_info (type, spaces);
- gdb_puts ("\n");
- break;
+ case TYPE_SPECIFIC_FIXED_POINT:
+ gdb_printf ("%*sfixed_point_info ", spaces, "");
+ print_fixed_point_type_info (type, spaces);
+ gdb_puts ("\n");
+ break;
case TYPE_SPECIFIC_INT:
if (type->bit_size_differs_p ())
--
2.40.1
reply other threads:[~2023-08-04 19:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230804195829.4128784-1-tromey@adacore.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
/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).