From: Simon Marchi <simon.marchi@ericsson.com>
To: <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@ericsson.com>
Subject: [pushed] Use bool in read_index_from_section
Date: Mon, 30 Apr 2018 15:08:00 -0000 [thread overview]
Message-ID: <1525100865-1748-1-git-send-email-simon.marchi@ericsson.com> (raw)
I happen to be working with this function, so I pushed this little obvious
patch.
gdb/ChangeLog:
* dwarf2read.c (read_index_from_section): Use bool.
---
gdb/ChangeLog | 4 ++++
gdb/dwarf2read.c | 6 +++---
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index bb80e1e..2a68a1b 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2018-04-30 Simon Marchi <simon.marchi@ericsson.com>
+
+ * dwarf2read.c (read_index_from_section): Use bool.
+
2018-04-29 Fabian Groffen <grobian@gentoo.org>
PR gdb/22950
diff --git a/gdb/dwarf2read.c b/gdb/dwarf2read.c
index 9eb98b2..fb10964 100644
--- a/gdb/dwarf2read.c
+++ b/gdb/dwarf2read.c
@@ -3411,7 +3411,7 @@ find_slot_in_mapped_hash (struct mapped_index *index, const char *name,
/* A helper function that reads the .gdb_index from SECTION and fills
in MAP. FILENAME is the name of the file containing the section;
- it is used for error reporting. DEPRECATED_OK is nonzero if it is
+ it is used for error reporting. DEPRECATED_OK is true if it is
ok to use deprecated sections.
CU_LIST, CU_LIST_ELEMENTS, TYPES_LIST, and TYPES_LIST_ELEMENTS are
@@ -3420,10 +3420,10 @@ find_slot_in_mapped_hash (struct mapped_index *index, const char *name,
Returns 1 if all went well, 0 otherwise. */
-static int
+static bool
read_index_from_section (struct objfile *objfile,
const char *filename,
- int deprecated_ok,
+ bool deprecated_ok,
struct dwarf2_section_info *section,
struct mapped_index *map,
const gdb_byte **cu_list,
--
2.7.4
reply other threads:[~2018-04-30 15:08 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=1525100865-1748-1-git-send-email-simon.marchi@ericsson.com \
--to=simon.marchi@ericsson.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).