aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2007-07-04 21:51:23 +0000
committerEli Zaretskii <eliz@gnu.org>2007-07-04 21:51:23 +0000
commit5fc14d0a92ceb7fc82607cf7186e3629d9bab273 (patch)
tree45599799f0bfea9633197c76556cfe66a791b826
parent0fdf1951981eafd070b503e8dab596d7c9ad07a7 (diff)
downloadbinutils-5fc14d0a92ceb7fc82607cf7186e3629d9bab273.zip
binutils-5fc14d0a92ceb7fc82607cf7186e3629d9bab273.tar.gz
binutils-5fc14d0a92ceb7fc82607cf7186e3629d9bab273.tar.bz2
(Target Conditionals): Fix last change.
-rw-r--r--gdb/doc/ChangeLog4
-rw-r--r--gdb/doc/gdbint.texinfo9
2 files changed, 8 insertions, 5 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index c98ed6b..27d63d9 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,7 @@
+2007-07-05 Eli Zaretskii <eliz@gnu.org>
+
+ * gdbint.texinfo (Target Conditionals): Fix last change.
+
2007-07-03 Markus Deuling <deuling@de.ibm.com>
* gdb.texinfo: Replace following macros by their appropriate gdbarch
diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo
index 0518f96..cfc141f 100644
--- a/gdb/doc/gdbint.texinfo
+++ b/gdb/doc/gdbint.texinfo
@@ -2584,7 +2584,6 @@ using the Bourne shell script @file{gdbarch.sh}.
* Compiler Characteristics::
* Target Conditionals::
* Adding a New Target::
-* Converting Targets to Multi-arch::
@end menu
@node OS ABI Variant Handling
@@ -3427,7 +3426,7 @@ program encounters a breakpoint. This is often the number of bytes in
If defined, this should evaluate to 1 if @var{addr} is in a shared
library in which breakpoints cannot be set and so should be disabled.
-@item void gdbarch_print_float_info (@var{gdbarch}, @var{file}, @var{frame},var{args})
+@item void gdbarch_print_float_info (@var{gdbarch}, @var{file}, @var{frame}, @var{args})
@findex gdbarch_print_float_info
If defined, then the @samp{info float} command will print information about
the processor's floating point unit.
@@ -3507,14 +3506,14 @@ Otherwise return 0.
Define this to adjust @var{address} so that it meets the alignment
requirements for the start of a new stack frame. A stack frame's
alignment requirements are typically stronger than a target processors
-stack alignment requirements (@pxref{DEPRECATED_STACK_ALIGN}).
+stack alignment requirements.
This function is used to ensure that, when creating a dummy frame, both
the initial stack pointer and (if needed) the address of the return
value are correctly aligned.
-Unlike @code{DEPRECATED_STACK_ALIGN}, this function always adjusts the
-address in the direction of stack growth.
+This function always adjusts the address in the direction of stack
+growth.
By default, no frame based stack alignment is performed.