diff options
| -rw-r--r-- | gdb/ChangeLog | 5 | ||||
| -rw-r--r-- | gdb/target.h | 11 |
2 files changed, 5 insertions, 11 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 914d32b..75b1d80 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,8 @@ +2001-11-20 Jim Blandy <jimb@redhat.com> + + * target.h (TARGET_RANGE_PROFITABLE_FOR_HW_WATCHPOINT): Delete + default definition; this is never used. + 2001-11-20 Keith Seitz <keiths@redhat.com> * varobj.c (c_value_of_child): Release memory for "name" when diff --git a/gdb/target.h b/gdb/target.h index 7c97ba6..18635d2 100644 --- a/gdb/target.h +++ b/gdb/target.h @@ -1049,17 +1049,6 @@ extern void (*target_new_objfile_hook) (struct objfile *); ((LONGEST)(byte_count) <= REGISTER_SIZE) #endif -/* However, some addresses may not be profitable to use hardware to watch, - or may be difficult to understand when the addressed object is out of - scope, and hence should be unwatched. On some targets, this may have - severe performance penalties, such that we might as well use regular - watchpoints, and save (possibly precious) hardware watchpoints for other - locations. */ - -#if !defined(TARGET_RANGE_PROFITABLE_FOR_HW_WATCHPOINT) -#define TARGET_RANGE_PROFITABLE_FOR_HW_WATCHPOINT(pid,start,len) 0 -#endif - /* Set/clear a hardware watchpoint starting at ADDR, for LEN bytes. TYPE is 0 for write, 1 for read, and 2 for read/write accesses. Returns 0 for |