Remove comments on software_single_step in gdbarch.sh
Commit Message
This comment is out of date. We've already done that. Patch is to remove
it.
gdb:
2016-03-21 Yao Qi <yao.qi@linaro.org>
* gdbarch.sh (software_single_step): Remove comments.
* gdbarch.h: Regenerated.
---
gdb/gdbarch.h | 4 ----
gdb/gdbarch.sh | 4 ----
2 files changed, 8 deletions(-)
Comments
Yao Qi <qiyaoltc@gmail.com> writes:
> This comment is out of date. We've already done that. Patch is to remove
> it.
>
> gdb:
>
> 2016-03-21 Yao Qi <yao.qi@linaro.org>
>
> * gdbarch.sh (software_single_step): Remove comments.
> * gdbarch.h: Regenerated.
Patch is pushed in.
@@ -646,10 +646,6 @@ extern void set_gdbarch_addr_bits_remove (struct gdbarch *gdbarch, gdbarch_addr_
indicates if the target needs software single step. An ISA method to
implement it.
- FIXME/cagney/2001-01-18: This should be replaced with something that inserts
- breakpoints using the breakpoint system instead of blatting memory directly
- (as with rs6000).
-
FIXME/cagney/2001-01-18: The logic is backwards. It should be asking if the
target can single step. If not, then implement single step using breakpoints.
@@ -605,10 +605,6 @@ m:CORE_ADDR:addr_bits_remove:CORE_ADDR addr:addr::core_addr_identity::0
# indicates if the target needs software single step. An ISA method to
# implement it.
#
-# FIXME/cagney/2001-01-18: This should be replaced with something that inserts
-# breakpoints using the breakpoint system instead of blatting memory directly
-# (as with rs6000).
-#
# FIXME/cagney/2001-01-18: The logic is backwards. It should be asking if the
# target can single step. If not, then implement single step using breakpoints.
#