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 call to dwarf2_per_objfile::adjust from read_call_site_scope Date: Sat, 4 May 2024 16:07:08 +0000 (GMT) [thread overview] Message-ID: <20240504160708.352393858283@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6142f7cd83643ec4e086d926a135844a912c3053 commit 6142f7cd83643ec4e086d926a135844a912c3053 Author: Tom Tromey <tom@tromey.com> Date: Mon Apr 1 17:05:18 2024 -0600 Remove call to dwarf2_per_objfile::adjust from read_call_site_scope read_call_site_scope does not need to call 'adjust', because in general the call site is not a symbol address, but rather just the address of some particular call. Diff: --- gdb/dwarf2/read.c | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c index 76330d7b784..7caacd25474 100644 --- a/gdb/dwarf2/read.c +++ b/gdb/dwarf2/read.c @@ -10231,7 +10231,7 @@ read_call_site_scope (struct die_info *die, struct dwarf2_cu *cu) sect_offset_str (die->sect_off), objfile_name (objfile)); return; } - unrelocated_addr pc = per_objfile->adjust (attr->as_address ()); + unrelocated_addr pc = attr->as_address (); if (cu->call_site_htab == NULL) cu->call_site_htab = htab_create_alloc_ex (16, call_site::hash, @@ -10406,10 +10406,7 @@ read_call_site_scope (struct die_info *die, struct dwarf2_cu *cu) "low pc, for referencing DIE %s [in module %s]"), sect_offset_str (die->sect_off), objfile_name (objfile)); else - { - lowpc = per_objfile->adjust (lowpc); - call_site->target.set_loc_physaddr (lowpc); - } + call_site->target.set_loc_physaddr (lowpc); } } else
reply other threads:[~2024-05-04 16:07 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=20240504160708.352393858283@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).