aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc/stabs.texinfo
diff options
context:
space:
mode:
authorJim Kingdon <jkingdon@engr.sgi.com>1994-02-02 16:33:09 +0000
committerJim Kingdon <jkingdon@engr.sgi.com>1994-02-02 16:33:09 +0000
commita9a4aec834d2050319d75e4275c0bea64e542545 (patch)
treec62bc24df509b9c65ede9e88f3d0a921b4694b0c /gdb/doc/stabs.texinfo
parentcd41d0672a98e7df45ed073d9504bd0cdfd1af4e (diff)
downloadgdb-a9a4aec834d2050319d75e4275c0bea64e542545.zip
gdb-a9a4aec834d2050319d75e4275c0bea64e542545.tar.gz
gdb-a9a4aec834d2050319d75e4275c0bea64e542545.tar.bz2
* stabs.texinfo (Negative Type Numbers): Document format for type
-16.
Diffstat (limited to 'gdb/doc/stabs.texinfo')
-rw-r--r--gdb/doc/stabs.texinfo6
1 files changed, 3 insertions, 3 deletions
diff --git a/gdb/doc/stabs.texinfo b/gdb/doc/stabs.texinfo
index b5beccb..85c2d4e 100644
--- a/gdb/doc/stabs.texinfo
+++ b/gdb/doc/stabs.texinfo
@@ -1543,9 +1543,9 @@ use a new negative type number.
@code{integer}. 32 bit signed integral type.
@item -16
-@code{boolean}. 32 bit type. How is the truth value encoded? Is it
-the least significant bit or is it a question of whether the whole value
-is zero or non-zero?
+@code{boolean}. 32 bit type. GDB and GCC assume that zero is false,
+one is true, and other values have unspecified meaning. I hope this
+agrees with how the IBM tools use the type.
@item -17
@code{short real}. IEEE single precision.