public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Remove a nullptr check in DWARF scanner Date: Mon, 17 Oct 2022 19:00:11 +0000 (GMT) [thread overview] Message-ID: <20221017190011.DB7AF3858D32@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=069355439fca1702c2440678663d1d0d40bbb735 commit 069355439fca1702c2440678663d1d0d40bbb735 Author: Tom Tromey <tromey@adacore.com> Date: Mon Oct 17 12:46:21 2022 -0600 Remove a nullptr check in DWARF scanner In scan_attributes, The DWARF scanner checks whether maybe_defer is nullptr, but this can never happen. This patch removes the check. Diff: --- gdb/dwarf2/read.c | 1 - 1 file changed, 1 deletion(-) diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c index 33dfd52b362..b5efcb3cc09 100644 --- a/gdb/dwarf2/read.c +++ b/gdb/dwarf2/read.c @@ -18217,7 +18217,6 @@ cooked_indexer::scan_attributes (dwarf2_per_cu_data *scanning_per_cu, if (new_reader->cu == reader->cu && new_info_ptr > watermark_ptr - && maybe_defer != nullptr && *parent_entry == nullptr) *maybe_defer = form_addr (origin_offset, origin_is_dwz); else if (*parent_entry == nullptr)
reply other threads:[~2022-10-17 19:00 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=20221017190011.DB7AF3858D32@sourceware.org \ --to=tromey@sourceware.org \ --cc=gdb-cvs@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: linkBe 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).