This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[docs] small gdb internals cleanup
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Date: Sun, 28 Dec 2008 18:09:25 +0000
- Subject: [docs] small gdb internals cleanup
The Native Conditionals sections talks about several native preprocessor
defines. CHILD_PREPARE_TO_STORE and FETCH_INFERIOR_REGISTERS are no
longer to be defined as macros. gdbarch_fp0_regnum is now properly a target
arch property so the description should move to the Target Conditionals
section; gdbarch_get_longjmp_target is already described there as such.
Ok to apply? I don't know where to draw the line on what obvious is
regarding the docs.
--
Pedro Alves
2008-12-28 Pedro Alves <pedro@codesourcery.com>
* gdbint.texinfo (gdbarch_cannot_fetch_register): Don't mention
FETCH_INFERIOR_REGISTERS.
(Native Conditionals): Remove obsolete CHILD_PREPARE_TO_STORE,
FETCH_INFERIOR_REGISTERS descriptions. Remove
gdbarch_get_longjmp_target descrition, since already described in
Target Conditionals. Move gdbarch_fp0_regnum description to ...
(Target Conditionals): ... here.
---
gdb/doc/gdbint.texinfo | 39 ++++++---------------------------------
1 file changed, 6 insertions(+), 33 deletions(-)
Index: src/gdb/doc/gdbint.texinfo
===================================================================
--- src.orig/gdb/doc/gdbint.texinfo 2008-12-28 17:44:45.000000000 +0000
+++ src/gdb/doc/gdbint.texinfo 2008-12-28 17:45:17.000000000 +0000
@@ -3509,8 +3509,7 @@ This method has been replaced by @code{g
@item int gdbarch_cannot_fetch_register (@var{gdbarch}, @var{regum})
@findex gdbarch_cannot_fetch_register
This function should return nonzero if @var{regno} cannot be fetched
-from an inferior process. This is only relevant if
-@code{FETCH_INFERIOR_REGISTERS} is not defined.
+from an inferior process.
@item int gdbarch_cannot_store_register (@var{gdbarch}, @var{regnum})
@findex gdbarch_cannot_store_register
@@ -3525,6 +3524,11 @@ Return non-zero if register @var{regnum}
@var{type} in a non-standard form.
@xref{Target Architecture Definition, , Using Different Register and Memory Data Representations}.
+@item int gdbarch_fp0_regnum (@var{gdbarch})
+@findex gdbarch_fp0_regnum
+This function returns the number of the first floating point register,
+if the machine has such registers. Otherwise, it returns -1.
+
@item CORE_ADDR gdbarch_decr_pc_after_break (@var{gdbarch})
@findex gdbarch_decr_pc_after_break
This function shall return the amount by which to decrement the PC after the
@@ -4517,37 +4521,6 @@ undefined) in @file{nm-@var{system}.h}.
@table @code
-@item CHILD_PREPARE_TO_STORE
-@findex CHILD_PREPARE_TO_STORE
-If the machine stores all registers at once in the child process, then
-define this to ensure that all values are correct. This usually entails
-a read from the child.
-
-[Note that this is incorrectly defined in @file{xm-@var{system}.h} files
-currently.]
-
-@item FETCH_INFERIOR_REGISTERS
-@findex FETCH_INFERIOR_REGISTERS
-Define this if the native-dependent code will provide its own routines
-@code{fetch_inferior_registers} and @code{store_inferior_registers} in
-@file{@var{host}-nat.c}. If this symbol is @emph{not} defined, and
-@file{infptrace.c} is included in this configuration, the default
-routines in @file{infptrace.c} are used for these functions.
-
-@item int gdbarch_fp0_regnum (@var{gdbarch})
-@findex gdbarch_fp0_regnum
-This functions normally returns the number of the first floating
-point register, if the machine has such registers. As such, it would
-appear only in target-specific code. However, @file{/proc} support uses this
-to decide whether floats are in use on this target.
-
-@item int gdbarch_get_longjmp_target (@var{gdbarch})
-@findex gdbarch_get_longjmp_target
-This function determines the target PC address that @code{longjmp} will jump to,
-assuming that we have just stopped at a longjmp breakpoint. It takes a
-@code{CORE_ADDR *} as argument, and stores the target PC value through this
-pointer. It examines the current state of the machine as needed.
-
@item I386_USE_GENERIC_WATCHPOINTS
An x86-based machine can define this to use the generic x86 watchpoint
support; see @ref{Algorithms, I386_USE_GENERIC_WATCHPOINTS}.