From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 2/2] [gdb/symtab] Fix two style issues in gdb/dwarf2/index-write.c
Date: Wed, 11 Oct 2023 17:32:14 +0200 [thread overview]
Message-ID: <20231011153214.25769-2-tdevries@suse.de> (raw)
In-Reply-To: <20231011153214.25769-1-tdevries@suse.de>
While reviewing gdb/dwarf2/index-write.c I noticed two style issues.
Fix these.
Tested on x86_64-linux.
---
gdb/dwarf2/index-write.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gdb/dwarf2/index-write.c b/gdb/dwarf2/index-write.c
index 6a21af80c3f..bac4a6c6934 100644
--- a/gdb/dwarf2/index-write.c
+++ b/gdb/dwarf2/index-write.c
@@ -1300,8 +1300,8 @@ write_gdbindex (dwarf2_per_bfd *per_bfd, cooked_index *table,
data_buf shortcuts;
write_shortcuts_table (table, shortcuts, constant_pool);
- write_gdbindex_1(out_file, objfile_cu_list, types_cu_list, addr_vec,
- symtab_vec, constant_pool, shortcuts);
+ write_gdbindex_1 (out_file, objfile_cu_list, types_cu_list, addr_vec,
+ symtab_vec, constant_pool, shortcuts);
if (dwz_out_file != NULL)
write_gdbindex_1 (dwz_out_file, dwz_cu_list, {}, {}, {}, {}, {});
@@ -1575,7 +1575,7 @@ save_gdb_index_command (const char *arg, int from_tty)
_("Error while writing index for `%s': "),
objfile_name (objfile));
}
- }
+ }
}
}
--
2.35.3
next prev parent reply other threads:[~2023-10-11 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 15:32 [PATCH 1/2] [gdb/symtab] Fix style issues in v9 .gdb_index section support Tom de Vries
2023-10-11 15:32 ` Tom de Vries [this message]
2023-10-17 20:07 ` [PATCH 2/2] [gdb/symtab] Fix two style issues in gdb/dwarf2/index-write.c 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
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=20231011153214.25769-2-tdevries@suse.de \
--to=tdevries@suse.de \
--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).