diff options
| author | Andrew Cagney <cagney@redhat.com> | 2002-04-06 00:02:52 +0000 |
|---|---|---|
| committer | Andrew Cagney <cagney@redhat.com> | 2002-04-06 00:02:52 +0000 |
| commit | 8227c0ffb14b297b1e53aa5154880d29f24103be (patch) | |
| tree | ab1814cb32edcbf904bb2f468329034f10cc2191 /gdb/ia64-tdep.c | |
| parent | 6adce8c596c8e29be5541524816b8ef6e07ece2e (diff) | |
| download | gdb-8227c0ffb14b297b1e53aa5154880d29f24103be.zip gdb-8227c0ffb14b297b1e53aa5154880d29f24103be.tar.gz gdb-8227c0ffb14b297b1e53aa5154880d29f24103be.tar.bz2 | |
* h8500-tdep.c (h8500_write_fp): Delete function.
* dwarf2cfi.c (cfi_write_fp): Document as not used.
* mips-tdep.c (mips_gdbarch_init): Do not set write_fp.
* ia64-tdep.c (ia64_gdbarch_init): Do not set write_fp.
* m68hc11-tdep.c (m68hc11_gdbarch_init): Do not set write_fp.
* rs6000-tdep.c (rs6000_gdbarch_init): Do not set write_fp.
* s390-tdep.c (s390_gdbarch_init): Do not set write_fp.
(s390_write_fp):
* sh-tdep.c (sh_gdbarch_init): Do not set write_fp.
* x86-64-tdep.c (i386_gdbarch_init): Do not set write_fp.
* d10v-tdep.c (d10v_gdbarch_init): Do not set write_fp.
(d10v_write_fp): Delete function.
* inferior.h (write_fp, generic_target_write_fp): Delete
declarations.
* regcache.c (generic_target_write_fp): Delete function.
(write_fp): Delete function.
* gdbarch.sh (TARGET_WRITE_FP): Delete.
* gdbarch.h, gdbarch.c: Regenerate.
* config/v850/tm-v850.h (TARGET_WRITE_FP): Delete macro.
* config/sparc/tm-sp64.h (TARGET_WRITE_FP): Delete macro.
(sparc64_write_fp): Delete declaration.
* config/h8500/tm-h8500.h (TARGET_WRITE_FP): Delete macro.
(h8500_write_fp): Delete declaration.
Diffstat (limited to 'gdb/ia64-tdep.c')
| -rw-r--r-- | gdb/ia64-tdep.c | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/gdb/ia64-tdep.c b/gdb/ia64-tdep.c index db8e5b9..18cd6ff 100644 --- a/gdb/ia64-tdep.c +++ b/gdb/ia64-tdep.c @@ -667,10 +667,9 @@ rse_address_add(CORE_ADDR addr, int nslots) even really hard to compute the frame chain, but it can be computationally expensive. So, instead of making life difficult (and slow), we pick a more convenient representation of the frame - chain, knowing that we'll have to make some small adjustments - in other places. (E.g, note that read_fp() and write_fp() are - actually read_sp() and write_sp() below in ia64_gdbarch_init() - below.) + chain, knowing that we'll have to make some small adjustments in + other places. (E.g, note that read_fp() is actually read_sp() in + ia64_gdbarch_init() below.) Okay, so what is the frame chain exactly? It'll be the SP value at the time that the function in question was entered. @@ -2204,7 +2203,6 @@ ia64_gdbarch_init (struct gdbarch_info info, struct gdbarch_list *arches) is all read_fp() is used for), simply use the stack pointer value instead. */ set_gdbarch_read_fp (gdbarch, generic_target_read_sp); - set_gdbarch_write_fp (gdbarch, generic_target_write_sp); /* Settings that should be unnecessary. */ set_gdbarch_inner_than (gdbarch, core_addr_lessthan); |