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] Rename write_psymtabs_to_index Date: Tue, 12 Apr 2022 15:41:17 +0000 (GMT) [thread overview] Message-ID: <20220412154117.0B1743858407@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=58f707487b8b67237dd798c48c098c7fb21f03bb commit 58f707487b8b67237dd798c48c098c7fb21f03bb Author: Tom Tromey <tom@tromey.com> Date: Thu May 27 14:52:11 2021 -0600 Rename write_psymtabs_to_index We'll be removing all the psymtab code from the DWARF reader. As a preparatory step, this renames write_psymtabs_to_index to avoid the "psymtab" name. Diff: --- gdb/dwarf2/index-cache.c | 6 +++--- gdb/dwarf2/index-write.c | 10 +++++----- gdb/dwarf2/index-write.h | 2 +- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/gdb/dwarf2/index-cache.c b/gdb/dwarf2/index-cache.c index db9a6eb5630..18e60cbd78c 100644 --- a/gdb/dwarf2/index-cache.c +++ b/gdb/dwarf2/index-cache.c @@ -148,9 +148,9 @@ index_cache::store (dwarf2_per_objfile *per_objfile) /* Write the index itself to the directory, using the build id as the filename. */ - write_psymtabs_to_index (per_objfile, m_dir.c_str (), - build_id_str.c_str (), dwz_build_id_ptr, - dw_index_kind::GDB_INDEX); + write_dwarf_index (per_objfile, m_dir.c_str (), + build_id_str.c_str (), dwz_build_id_ptr, + dw_index_kind::GDB_INDEX); } catch (const gdb_exception_error &except) { diff --git a/gdb/dwarf2/index-write.c b/gdb/dwarf2/index-write.c index 7a6bc24a3e6..95202db2810 100644 --- a/gdb/dwarf2/index-write.c +++ b/gdb/dwarf2/index-write.c @@ -1577,9 +1577,9 @@ struct index_wip_file /* See dwarf-index-write.h. */ void -write_psymtabs_to_index (dwarf2_per_objfile *per_objfile, const char *dir, - const char *basename, const char *dwz_basename, - dw_index_kind index_kind) +write_dwarf_index (dwarf2_per_objfile *per_objfile, const char *dir, + const char *basename, const char *dwz_basename, + dw_index_kind index_kind) { dwarf2_per_bfd *per_bfd = per_objfile->per_bfd; struct objfile *objfile = per_objfile->objfile; @@ -1675,8 +1675,8 @@ save_gdb_index_command (const char *arg, int from_tty) if (dwz != NULL) dwz_basename = lbasename (dwz->filename ()); - write_psymtabs_to_index (per_objfile, arg, basename, dwz_basename, - index_kind); + write_dwarf_index (per_objfile, arg, basename, dwz_basename, + index_kind); } catch (const gdb_exception_error &except) { diff --git a/gdb/dwarf2/index-write.h b/gdb/dwarf2/index-write.h index 0fbae38f530..b8855dcae7c 100644 --- a/gdb/dwarf2/index-write.h +++ b/gdb/dwarf2/index-write.h @@ -32,7 +32,7 @@ derived from INDEX_KIND is added to this base name. DWZ_BASENAME is the same, but for the dwz file's index. */ -extern void write_psymtabs_to_index +extern void write_dwarf_index (dwarf2_per_objfile *per_objfile, const char *dir, const char *basename, const char *dwz_basename, dw_index_kind index_kind);
reply other threads:[~2022-04-12 15:41 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=20220412154117.0B1743858407@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).