From: John Baldwin <jhb@FreeBSD.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 4/5] arm-fbsd: Use a static regset for the TLS register set.
Date: Thu, 7 Jul 2022 17:58:15 -0700 [thread overview]
Message-ID: <20220708005816.9408-5-jhb@FreeBSD.org> (raw)
In-Reply-To: <20220708005816.9408-1-jhb@FreeBSD.org>
This uses custom collect/supply regset handlers which pass the TLS
register number from the gdbarch_tdep as the base register number.
---
gdb/arm-fbsd-nat.c | 34 ++++-------------------------
gdb/arm-fbsd-tdep.c | 52 +++++++++++++++++++++++++++++++--------------
gdb/arm-fbsd-tdep.h | 1 +
3 files changed, 41 insertions(+), 46 deletions(-)
diff --git a/gdb/arm-fbsd-nat.c b/gdb/arm-fbsd-nat.c
index a306e1e2ee0..ceda6337ab9 100644
--- a/gdb/arm-fbsd-nat.c
+++ b/gdb/arm-fbsd-nat.c
@@ -58,21 +58,8 @@ arm_fbsd_nat_target::fetch_registers (struct regcache *regcache, int regnum)
arm_gdbarch_tdep *tdep = (arm_gdbarch_tdep *) gdbarch_tdep (gdbarch);
if (tdep->tls_regnum > 0)
- {
- const struct regcache_map_entry arm_fbsd_tlsregmap[] =
- {
- { 1, tdep->tls_regnum, 4 },
- { 0 }
- };
-
- const struct regset arm_fbsd_tlsregset =
- {
- arm_fbsd_tlsregmap,
- regcache_supply_regset, regcache_collect_regset
- };
-
- fetch_regset<uint32_t> (regcache, regnum, NT_ARM_TLS, &arm_fbsd_tlsregset);
- }
+ fetch_regset<uint32_t> (regcache, regnum, NT_ARM_TLS, &arm_fbsd_tls_regset,
+ tdep->tls_regnum);
#endif
}
@@ -93,21 +80,8 @@ arm_fbsd_nat_target::store_registers (struct regcache *regcache, int regnum)
arm_gdbarch_tdep *tdep = (arm_gdbarch_tdep *) gdbarch_tdep (gdbarch);
if (tdep->tls_regnum > 0)
- {
- const struct regcache_map_entry arm_fbsd_tlsregmap[] =
- {
- { 1, tdep->tls_regnum, 4 },
- { 0 }
- };
-
- const struct regset arm_fbsd_tlsregset =
- {
- arm_fbsd_tlsregmap,
- regcache_supply_regset, regcache_collect_regset
- };
-
- store_regset<uint32_t> (regcache, regnum, NT_ARM_TLS, &arm_fbsd_tlsregset);
- }
+ store_regset<uint32_t> (regcache, regnum, NT_ARM_TLS, &arm_fbsd_tls_regset,
+ tdep->tls_regnum);
#endif
}
diff --git a/gdb/arm-fbsd-tdep.c b/gdb/arm-fbsd-tdep.c
index 483820c1092..2a73643b763 100644
--- a/gdb/arm-fbsd-tdep.c
+++ b/gdb/arm-fbsd-tdep.c
@@ -52,6 +52,12 @@ static const struct regcache_map_entry arm_fbsd_vfpregmap[] =
{ 0 }
};
+static const struct regcache_map_entry arm_fbsd_tls_regmap[] =
+ {
+ { 1, 0, 4 },
+ { 0 }
+ };
+
/* In a signal frame, sp points to a 'struct sigframe' which is
defined as:
@@ -151,6 +157,34 @@ const struct regset arm_fbsd_vfpregset =
regcache_supply_regset, regcache_collect_regset
};
+static void
+arm_fbsd_supply_tls_regset (const struct regset *regset,
+ struct regcache *regcache,
+ int regnum, const void *buf, size_t size)
+{
+ struct gdbarch *gdbarch = regcache->arch ();
+ arm_gdbarch_tdep *tdep = (arm_gdbarch_tdep *) gdbarch_tdep (gdbarch);
+
+ regcache->supply_regset (regset, tdep->tls_regnum, regnum, buf, size);
+}
+
+static void
+arm_fbsd_collect_tls_regset (const struct regset *regset,
+ const struct regcache *regcache,
+ int regnum, void *buf, size_t size)
+{
+ struct gdbarch *gdbarch = regcache->arch ();
+ arm_gdbarch_tdep *tdep = (arm_gdbarch_tdep *) gdbarch_tdep (gdbarch);
+
+ regcache->collect_regset (regset, tdep->tls_regnum, regnum, buf, size);
+}
+
+const struct regset arm_fbsd_tls_regset =
+ {
+ arm_fbsd_tls_regmap,
+ arm_fbsd_supply_tls_regset, arm_fbsd_collect_tls_regset
+ };
+
/* Implement the "iterate_over_regset_sections" gdbarch method. */
static void
@@ -165,22 +199,8 @@ arm_fbsd_iterate_over_regset_sections (struct gdbarch *gdbarch,
&arm_fbsd_gregset, NULL, cb_data);
if (tdep->tls_regnum > 0)
- {
- const struct regcache_map_entry arm_fbsd_tlsregmap[] =
- {
- { 1, tdep->tls_regnum, 4 },
- { 0 }
- };
-
- const struct regset arm_fbsd_tlsregset =
- {
- arm_fbsd_tlsregmap,
- regcache_supply_regset, regcache_collect_regset
- };
-
- cb (".reg-aarch-tls", ARM_FBSD_SIZEOF_TLSREGSET, ARM_FBSD_SIZEOF_TLSREGSET,
- &arm_fbsd_tlsregset, NULL, cb_data);
- }
+ cb (".reg-aarch-tls", ARM_FBSD_SIZEOF_TLSREGSET, ARM_FBSD_SIZEOF_TLSREGSET,
+ &arm_fbsd_tls_regset, NULL, cb_data);
/* While FreeBSD/arm cores do contain a NT_FPREGSET / ".reg2"
register set, it is not populated with register values by the
diff --git a/gdb/arm-fbsd-tdep.h b/gdb/arm-fbsd-tdep.h
index 193eb76df3c..923b749367e 100644
--- a/gdb/arm-fbsd-tdep.h
+++ b/gdb/arm-fbsd-tdep.h
@@ -35,6 +35,7 @@
extern const struct regset arm_fbsd_gregset;
extern const struct regset arm_fbsd_vfpregset;
+extern const struct regset arm_fbsd_tls_regset;
/* Flags passed in AT_HWCAP. */
#define HWCAP_VFP 0x00000040
--
2.36.1
next prev parent reply other threads:[~2022-07-08 1:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 0:58 [PATCH 0/5] Improve support for regcache_map_entry with variable register base John Baldwin
2022-07-08 0:58 ` [PATCH 1/5] regcache: Add collect/supply_regset variants that accept a " John Baldwin
2022-11-22 19:56 ` Simon Marchi
2022-11-22 20:18 ` Simon Marchi
2022-11-22 22:32 ` John Baldwin
2022-07-08 0:58 ` [PATCH 2/5] fbsd-nat: Use regset supply/collect methods John Baldwin
2022-11-22 20:20 ` Simon Marchi
2022-07-08 0:58 ` [PATCH 3/5] fbsd-nat: Pass an optional register base to the register set helpers John Baldwin
2022-11-22 20:38 ` Simon Marchi
2022-11-22 22:16 ` John Baldwin
2022-11-22 22:25 ` John Baldwin
2022-07-08 0:58 ` John Baldwin [this message]
2022-11-22 20:39 ` [PATCH 4/5] arm-fbsd: Use a static regset for the TLS register set Simon Marchi
2022-07-08 0:58 ` [PATCH 5/5] aarch64-fbsd: " John Baldwin
2022-11-22 20:40 ` Simon Marchi
2022-07-21 14:53 ` [PATCH 0/5] Improve support for regcache_map_entry with variable register base John Baldwin
2022-08-22 18:11 ` [PING] " John Baldwin
2022-09-20 17:50 ` John Baldwin
2022-10-20 20:26 ` [PING 4] " John Baldwin
2022-11-21 18:21 ` [PING 5] " John Baldwin
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=20220708005816.9408-5-jhb@FreeBSD.org \
--to=jhb@freebsd.org \
--cc=gdb-patches@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: link
Be 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).