aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc
diff options
context:
space:
mode:
Diffstat (limited to 'gdb/doc')
-rw-r--r--gdb/doc/ChangeLog4
-rw-r--r--gdb/doc/remote.texi22
2 files changed, 21 insertions, 5 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 7af9c45..ba926d1 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,7 @@
+Tue Jan 17 14:09:03 1995 Ian Lance Taylor <ian@sanguine.cygnus.com>
+
+ * remote.texi: Update documentation of set/show mipsfpu.
+
start-sanitize-gdbtk
Fri Jan 6 17:17:28 1995 Stan Shebs <shebs@andros.cygnus.com>
diff --git a/gdb/doc/remote.texi b/gdb/doc/remote.texi
index 03407bd..9b43b86 100644
--- a/gdb/doc/remote.texi
+++ b/gdb/doc/remote.texi
@@ -1286,20 +1286,32 @@ concentrator) instead of a serial port, using the syntax
@value{GDBN} also supports these special commands for MIPS targets:
@table @code
-@item set mipsfpu off
+@item set mipsfpu double
+@itemx set mipsfpu single
+@itemx set mipsfpu none
@itemx show mipsfpu
-@kindex set mipsfpu off
+@kindex set mipsfpu
@kindex show mipsfpu
@cindex MIPS remote floating point
@cindex floating point, MIPS remote
If your target board does not support the MIPS floating point
-coprocessor, you should use the command @samp{set mipsfpu off} (if you
+coprocessor, you should use the command @samp{set mipsfpu none} (if you
need this, you may wish to put the command in your @value{GDBINIT}
file). This tells @value{GDBN} how to find the return value of
functions which return floating point values. It also allows
@value{GDBN} to avoid saving the floating point registers when calling
-functions on the board. (As usual, you can inquire about the
-@code{mipsfpu} variable with @samp{show mipsfpu}.)
+functions on the board. If you are using a floating point coprocessor
+with only single precision floating point support, as on the @sc{r4650}
+processor, use the command @samp{set mipsfpu single}. The default
+double precision floating point coprocessor may be selected using
+@samp{set mipsfpu double}.
+
+In previous versions the only choices were double precision or no
+floating point, so @samp{set mipsfpu on} will select double precision
+and @samp{set mipsfpu off} will select no floating point.
+
+As usual, you can inquire about the @code{mipsfpu} variable with
+@samp{show mipsfpu}.
@item set remotedebug @var{n}
@itemx show remotedebug