public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: John Baldwin <jhb@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] i386-fbsd-nat: Remove two unused variables. Date: Mon, 11 Apr 2022 18:03:27 +0000 (GMT) [thread overview] Message-ID: <20220411180327.9090F3858D1E@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=aa1402a95d209f4f45ad9489ca985c57662eac6c commit aa1402a95d209f4f45ad9489ca985c57662eac6c Author: John Baldwin <jhb@FreeBSD.org> Date: Mon Apr 11 11:00:01 2022 -0700 i386-fbsd-nat: Remove two unused variables. Earlier versions of the change in 1285ce8629b37f800bf21731ee7c7a8b1b8d0233 used this variable, but not the final version that landed. Diff: --- gdb/i386-fbsd-nat.c | 6 ------ 1 file changed, 6 deletions(-) diff --git a/gdb/i386-fbsd-nat.c b/gdb/i386-fbsd-nat.c index 4b8ba8b598f..0a00aef5901 100644 --- a/gdb/i386-fbsd-nat.c +++ b/gdb/i386-fbsd-nat.c @@ -60,9 +60,6 @@ void i386_fbsd_nat_target::fetch_registers (struct regcache *regcache, int regnum) { struct gdbarch *gdbarch = regcache->arch (); -#if defined(PT_GETFSBASE) || defined(PT_GETGSBASE) - const struct gdbarch_tdep *tdep = gdbarch_tdep (gdbarch); -#endif pid_t pid = get_ptrace_pid (regcache->ptid ()); if (fetch_register_set<struct reg> (regcache, regnum, PT_GETREGS, @@ -142,9 +139,6 @@ void i386_fbsd_nat_target::store_registers (struct regcache *regcache, int regnum) { struct gdbarch *gdbarch = regcache->arch (); -#if defined(PT_GETFSBASE) || defined(PT_GETGSBASE) - const struct gdbarch_tdep *tdep = gdbarch_tdep (gdbarch); -#endif pid_t pid = get_ptrace_pid (regcache->ptid ()); if (store_register_set<struct reg> (regcache, regnum, PT_GETREGS, PT_SETREGS,
reply other threads:[~2022-04-11 18:03 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=20220411180327.9090F3858D1E@sourceware.org \ --to=jhb@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).