diff options
| author | Andrew Cagney <cagney@redhat.com> | 2003-03-14 17:07:01 +0000 |
|---|---|---|
| committer | Andrew Cagney <cagney@redhat.com> | 2003-03-14 17:07:01 +0000 |
| commit | ac2adee56d30e7e7e3f92c07645f718dfce789f6 (patch) | |
| tree | 30810135c05018b8ba5f693d5b39205573d5e9ed /gdb/config | |
| parent | 129c1cd6c2eade2bef833eaf25a0e9b0de9ef946 (diff) | |
| download | gdb-ac2adee56d30e7e7e3f92c07645f718dfce789f6.zip gdb-ac2adee56d30e7e7e3f92c07645f718dfce789f6.tar.gz gdb-ac2adee56d30e7e7e3f92c07645f718dfce789f6.tar.bz2 | |
2003-03-12 Andrew Cagney <cagney@redhat.com>
* frame.c (get_saved_register): Delete function.
* xstormy16-tdep.c: Update comment.
* regcache.h: Update comments.
* sparc-tdep.c (sparc_init_extra_frame_info): Instead of
get_saved_register and extract_address, use
frame_read_unsigned_register.
(sparc_frame_saved_pc): Ditto.
(sparc_get_saved_register): Instead of get_saved_register, use
frame_register.
(sparc_pop_frame): Ditto.
* frame.h (get_saved_register): Delete declaration.
* findvar.c: Update comments.
(value_of_register): Call frame_register instead of
get_saved_register.
(value_from_register): Ditto.
* config/sparc/tm-sparc.h: Update comment.
* breakpoint.c: Update comment.
Index: doc/ChangeLog
2003-03-12 Andrew Cagney <cagney@redhat.com>
* gdbint.texinfo (Target Architecture Definition): Delete
references to get_saved_register.
Diffstat (limited to 'gdb/config')
| -rw-r--r-- | gdb/config/sparc/tm-sparc.h | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/gdb/config/sparc/tm-sparc.h b/gdb/config/sparc/tm-sparc.h index 5268713..8ab7401 100644 --- a/gdb/config/sparc/tm-sparc.h +++ b/gdb/config/sparc/tm-sparc.h @@ -199,10 +199,10 @@ extern int sparc_intreg_size (void); stack rather than with the other registers, and this causes hair and confusion in places like pop_frame. It might be better to remove the ins and locals from `registers', make sure that - get_saved_register can get them from the stack (even in the - innermost frame), and make this the way to access them. For the - frame pointer we would do that via TARGET_READ_FP. On the other - hand, that is likely to be confusing or worse for flat frames. */ + frame_register() can get them from the stack (even in the innermost + frame), and make this the way to access them. For the frame + pointer we would do that via TARGET_READ_FP. On the other hand, + that is likely to be confusing or worse for flat frames. */ #define REGISTER_BYTES (32*4+32*4+8*4) |