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 two unused fields from gdbarch Date: Tue, 17 Jan 2023 21:32:42 +0000 (GMT) [thread overview] Message-ID: <20230117213242.A94813858D28@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2c01dcdb5a2de09a5b36655f1a90d9471278d8b3 commit 2c01dcdb5a2de09a5b36655f1a90d9471278d8b3 Author: Tom Tromey <tromey@adacore.com> Date: Tue Jan 17 12:45:11 2023 -0700 Remove two unused fields from gdbarch When I converted gdbarch to use the registry, I forgot to remove the two fields that were used to implement the previous approach. This patch removes them. Tested by rebuilding. Diff: --- gdb/gdbarch.c | 4 ---- gdb/gdbarch.py | 4 ---- 2 files changed, 8 deletions(-) diff --git a/gdb/gdbarch.c b/gdb/gdbarch.c index 46baca9c479..04fcc92f8f9 100644 --- a/gdb/gdbarch.c +++ b/gdb/gdbarch.c @@ -48,10 +48,6 @@ struct gdbarch gdbarch_tdep_up tdep; gdbarch_dump_tdep_ftype *dump_tdep = nullptr; - /* per-architecture data-pointers. */ - unsigned nr_data = 0; - void **data = nullptr; - int short_bit = 2*TARGET_CHAR_BIT; int int_bit = 4*TARGET_CHAR_BIT; int long_bit = 4*TARGET_CHAR_BIT; diff --git a/gdb/gdbarch.py b/gdb/gdbarch.py index 7dc79386940..3ebc3598047 100755 --- a/gdb/gdbarch.py +++ b/gdb/gdbarch.py @@ -289,10 +289,6 @@ with open("gdbarch.c", "w") as f: print(" gdbarch_tdep_up tdep;", file=f) print(" gdbarch_dump_tdep_ftype *dump_tdep = nullptr;", file=f) print(file=f) - print(" /* per-architecture data-pointers. */", file=f) - print(" unsigned nr_data = 0;", file=f) - print(" void **data = nullptr;", file=f) - print(file=f) for c in filter(not_info, components): if isinstance(c, Function): print(f" gdbarch_{c.name}_ftype *", file=f, end="")
reply other threads:[~2023-01-17 21:32 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=20230117213242.A94813858D28@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).