* stabs.texinfo (Negative Type Numbers): FORTRAN LOGICAL fix.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 4255245da75f529f212d44e92815d6f519591e78..2bb689532c7aecab411058d09a7cd94328873337 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,7 @@
+Mon Jul 26 13:00:09 1993  Jim Kingdon  (kingdon@lioth.cygnus.com)
+
+       * stabs.texinfo (Negative Type Numbers): FORTRAN LOGICAL fix.
+
 Tue Jul 20 16:30:41 1993  Jim Kingdon  (kingdon@deneb.cygnus.com)
 
        * Makefile.in (refcard.dvi): Use srcdir where necessary.

diff --git a/gdb/doc/stabs.texinfo b/gdb/doc/stabs.texinfo
index 0e008cf408d8966c9d4a90af6f5df331a93cf070..979cebb6c2ce18fa8870571b8d1c2a1526e1123b 100644 (file)
--- a/gdb/doc/stabs.texinfo
+++ b/gdb/doc/stabs.texinfo
@@ -1354,14 +1354,15 @@ I'm not sure whether anyone has tried to define what this means if
 their customary size).  If @code{int} has exactly one size for each
 architecture, then it can be handled easily enough, but if the size of
 @code{int} can vary according the compiler options, then it gets hairy.
-I guess the consistent way to do this would be to define separate
-negative type numbers for 16-bit @code{int} and 32-bit @code{int};
-therefore I have indicated below the customary size (and other format
-information) for each type.  The information below is currently correct
-because AIX on the RS6000 is the only system which uses these type
-numbers.  If these type numbers start to get used on other systems, I
-suspect the correct thing to do is to define a new number in cases where
-a type does not have the size and format indicated below.
+The best way to do this would be to define separate negative type
+numbers for 16-bit @code{int} and 32-bit @code{int}; therefore I have
+indicated below the customary size (and other format information) for
+each type.  The information below is currently correct because AIX on
+the RS6000 is the only system which uses these type numbers.  If these
+type numbers start to get used on other systems, I suspect the correct
+thing to do is to define a new number in cases where a type does not
+have the size and format indicated below (or avoid negative type numbers
+in these cases).
 
 Also note that part of the definition of the negative type number is
 the name of the type.  Types with identical size and format but
@@ -1446,7 +1447,9 @@ is zero or non-zero?
 @code{logical*4}, 32 bit unsigned integral type.
 
 @item -24
-@code{logical}, 32 bit unsigned integral type.
+@code{logical}, 32 bit type.  This @sc{fortran} type has a split
+personality in that it is used for boolean variables, but can also be
+used for unsigned integers.
 
 @item -25
 @code{complex}.  A complex type consisting of two IEEE single-precision