diff options
| author | Markus Deuling <deuling@de.ibm.com> | 2008-02-18 16:37:17 +0000 |
|---|---|---|
| committer | Markus Deuling <deuling@de.ibm.com> | 2008-02-18 16:37:17 +0000 |
| commit | c2c4b923d5f677fa30928670c826d8506a7e288d (patch) | |
| tree | cafacefe90266f8ae6eab82c8b37dee7d913712c /gdb/regcache.h | |
| parent | 9215e42a5c4085dbe7375264069ec6d3f049ac8b (diff) | |
| download | gdb-c2c4b923d5f677fa30928670c826d8506a7e288d.tar.gz | |
* sentinel-frame.c (sentinel_frame_prev_register): Do not call
register_offset_hack anymore.
* regcache.{c,h} (register_offset_hack): Remove.
Diffstat (limited to 'gdb/regcache.h')
| -rw-r--r-- | gdb/regcache.h | 12 |
1 files changed, 0 insertions, 12 deletions
diff --git a/gdb/regcache.h b/gdb/regcache.h index 48edf53c23b..1e4ee86adc8 100644 --- a/gdb/regcache.h +++ b/gdb/regcache.h @@ -104,18 +104,6 @@ extern void regcache_raw_collect (const struct regcache *regcache, int regnum, void *buf); -/* The register's ``offset''. - - FIXME: cagney/2002-11-07: The frame_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); - - /* The type of a register. This function is slightly more efficient then its gdbarch vector counterpart since it returns a precomputed value stored in a table. */ |