diff options
| author | Ulrich Weigand <uweigand@de.ibm.com> | 2007-06-09 13:49:20 +0000 |
|---|---|---|
| committer | Ulrich Weigand <uweigand@de.ibm.com> | 2007-06-09 13:49:20 +0000 |
| commit | bf6ae4641c04121071734f45fd22b2ee2533d3b1 (patch) | |
| tree | f6862b215882e0410306eb5e626c366836ea1c2f /gdb/gdbarch.sh | |
| parent | c9f4d5725ddd4daae3866469aaa6293f1b58a404 (diff) | |
| download | binutils-gdb-bf6ae4641c04121071734f45fd22b2ee2533d3b1.tar.gz | |
2007-06-09 Markus Deuling <deuling@de.ibm.com>
* gdbarch.sh (ADDR_BITS_REMOVE): Replace by gdbarch_addr_bits_remove.
* value.c (value_as_address): Likewise (comment).
* remote-mips.c (common_breakpoint): Likewise.
* regcache.c (read_pc_pid): Likewise.
* printcmd.c (do_one_display): Likewise.
* monitor.c (monitor_write_memory, monitor_read_memory)
(monitor_insert_breakpoint): Likewise.
* mips-tdep.c (heuristic_proc_start): Likewise.
* infrun.c (insert_step_resume_breakpoint_at_frame)
(insert_step_resume_breakpoint_at_caller): Likewise.
* buildsym.c (record_line): Likewise.
* arm-tdep.c (arm_scan_prologue, thumb_get_next_pc)
(arm_get_next_pc): Likewise.
* armnbsd-nat.c (arm_supply_gregset, fetch_register, store_register)
(store_regs): Likewise.
* arm-linux-tdep.c (arm_linux_supply_gregset): Likewise.
* arm-linux-nat.c (fetch_register, fetch_regs): Likewise.
* gdbarch.c, gdbarch.h: Regenerate.
Diffstat (limited to 'gdb/gdbarch.sh')
| -rwxr-xr-x | gdb/gdbarch.sh | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/gdb/gdbarch.sh b/gdb/gdbarch.sh index a811f7b7749..4df1da66b20 100755 --- a/gdb/gdbarch.sh +++ b/gdb/gdbarch.sh @@ -588,16 +588,16 @@ v::int:frame_red_zone_size m::CORE_ADDR:convert_from_func_ptr_addr:CORE_ADDR addr, struct target_ops *targ:addr, targ::convert_from_func_ptr_addr_identity::0 # On some machines there are bits in addresses which are not really # part of the address, but are used by the kernel, the hardware, etc. -# for special purposes. ADDR_BITS_REMOVE takes out any such bits so +# for special purposes. gdbarch_addr_bits_remove takes out any such bits so # we get a "real" address such as one would find in a symbol table. # This is used only for addresses of instructions, and even then I'm # not sure it's used in all contexts. It exists to deal with there # being a few stray bits in the PC which would mislead us, not as some # sort of generic thing to handle alignment or segmentation (it's # possible it should be in TARGET_READ_PC instead). -f:=:CORE_ADDR:addr_bits_remove:CORE_ADDR addr:addr::core_addr_identity::0 +f::CORE_ADDR:addr_bits_remove:CORE_ADDR addr:addr::core_addr_identity::0 # It is not at all clear why SMASH_TEXT_ADDRESS is not folded into -# ADDR_BITS_REMOVE. +# gdbarch_addr_bits_remove. f:=:CORE_ADDR:smash_text_address:CORE_ADDR addr:addr::core_addr_identity::0 # FIXME/cagney/2001-01-18: This should be split in two. A target method that |