]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commit
gdb: use reg_buffer_common throughout gdbsupport/common-regcache.h
authorSimon Marchi <simon.marchi@efficios.com>
Fri, 1 Dec 2023 16:27:15 +0000 (11:27 -0500)
committerSimon Marchi <simon.marchi@efficios.com>
Thu, 14 Dec 2023 16:04:49 +0000 (16:04 +0000)
commite4e20d45110d919a5a2da2db84806f315ab59d90
treec153a7c86e48bbb61850d2dd0f230bef3ba8e9ae
parentc3a03de70fd373c0f8fc4ba5df1c0db29445112c
gdb: use reg_buffer_common throughout gdbsupport/common-regcache.h

Right now, gdbsupport/common-regcache.h contains two abstractons for a
regcache.  An opaque type `regcache` (gdb and gdbserver both have their
own regcache that is the concrete version of this) and an abstract base
class `reg_buffer_common`, that is the base of regcaches on both sides.
These abstractions allow code to be written for both gdb and gdbserver,
for instance in the gdb/arch sub-directory.

However, having two
different abstractions is impractical.  If some common code has a regcache,
and wants to use an operation defined on reg_buffer_common, it can't.
It would be better to have just one.  Change all instances of `regcache
*` in gdbsupport/common-regcache.h to be `reg_buffer_common *`, then fix
fallouts.

Implementations in gdb and gdbserver now need to down-cast (using
gdb::checked_static_cast) from reg_buffer_common to their concrete
regcache type.  Some of them could be avoided by changing free functions
(like regcache_register_size) to be virtual methods on
reg_buffer_common.  I tried it, it seems to work, but I did not include
it in this series to avoid adding unnecessary changes.

Change-Id: Ia5503adb6b5509a0f4604bd2a68b4642cc5283fd
Reviewed-by: John Baldwin <jhb@FreeBSD.org>
13 files changed:
gdb/arch/arm-get-next-pcs.c
gdb/arch/arm-get-next-pcs.h
gdb/arch/arm.c
gdb/arch/arm.h
gdb/arm-linux-tdep.c
gdb/arm-tdep.c
gdb/nat/aarch64-hw-point.c
gdb/nat/linux-btrace.c
gdb/regcache.c
gdbserver/linux-arm-low.cc
gdbserver/regcache.cc
gdbsupport/common-regcache.cc
gdbsupport/common-regcache.h