aboutsummaryrefslogtreecommitdiff
path: root/gdb/regcache.h
diff options
context:
space:
mode:
authorAndrew Cagney <cagney@redhat.com>2002-11-07 21:43:23 +0000
committerAndrew Cagney <cagney@redhat.com>2002-11-07 21:43:23 +0000
commite600bd345df96b0aca4005da435c21343f143890 (patch)
treee1895cee3ca0ece2fba00c2b9922d4f01a78e300 /gdb/regcache.h
parent568f87394bc2b35d5c4aeedc023fcaeb56138856 (diff)
downloadfsf-binutils-gdb-e600bd345df96b0aca4005da435c21343f143890.zip
fsf-binutils-gdb-e600bd345df96b0aca4005da435c21343f143890.tar.gz
fsf-binutils-gdb-e600bd345df96b0aca4005da435c21343f143890.tar.bz2
2002-11-07 Andrew Cagney <ac131313@redhat.com>
* regcache.h (regcache_cooked_read_using_offset_hack) (regcache_cooked_write_using_offset_hack): Delete declarations. (register_changed): Delete declaration. * regcache.c (regcache_cooked_read_using_offset_hack) (regcache_cooked_write_using_offset_hack): Delete functions. (cooked_xfer_using_offset_hack): Delete function. (register_changed): Delete function.
Diffstat (limited to 'gdb/regcache.h')
-rw-r--r--gdb/regcache.h29
1 files changed, 6 insertions, 23 deletions
diff --git a/gdb/regcache.h b/gdb/regcache.h
index 400ba85..ad70298 100644
--- a/gdb/regcache.h
+++ b/gdb/regcache.h
@@ -94,29 +94,14 @@ extern void regcache_collect (int regnum, void *buf);
/* The register's ``offset''.
- NOTE: cagney/2002-08-17: The ``struct value'' and expression
- evaluator treat the register cache as a large liner buffer.
- Instead of reading/writing a register using its register number,
- the code read/writes registers by specifying their offset into the
- buffer and a number of bytes. The code also assumes that these
- byte read/writes can cross register boundaries, adjacent registers
- treated as a contiguous set of bytes.
-
- The below map that model onto the real register cache. New code
- should go out of their way to avoid using these interfaces.
-
- FIXME: cagney/2002-08-17: The ``struct value'' and expression
- evaluator should be fixed. Instead of using the { offset, length }
- pair to describe a value within one or more registers, the code
- should use a chain of { regnum, offset, len } tripples. */
+ FIXME: cagney/2002-11-07: The get_saved_register() function, when
+ specifying the real location of a register, does so using that
+ registers offset in the register cache. That offset is then used
+ by valops.c to determine the location of the register. The code
+ should instead use the register's number and a location expression
+ to describe a value spread across multiple registers or memory. */
extern int register_offset_hack (struct gdbarch *gdbarch, int regnum);
-extern void regcache_cooked_read_using_offset_hack (struct regcache *regcache,
- int offset, int len,
- void *buf);
-extern void regcache_cooked_write_using_offset_hack (struct regcache *regcache,
- int offset, int len,
- const void *buf);
/* The type of a register. This function is slightly more efficient
@@ -201,8 +186,6 @@ extern int register_cached (int regnum);
extern void set_register_cached (int regnum, int state);
-extern void register_changed (int regnum);
-
extern void registers_changed (void);