FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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

Browse source
This commit is contained in:
Jim Kingdon 1993-07-26 18:14:20 +00:00
parent 6b93d764ca
commit 0e84d6ec2d
2 changed files with 16 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

4
gdb/doc/ChangeLog
View file

@ -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) Tue Jul 20 16:30:41 1993 Jim Kingdon (kingdon@deneb.cygnus.com)
* Makefile.in (refcard.dvi): Use srcdir where necessary. * Makefile.in (refcard.dvi): Use srcdir where necessary.

21
gdb/doc/stabs.texinfo
View file

@ -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 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 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. @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 The best way to do this would be to define separate negative type
negative type numbers for 16-bit @code{int} and 32-bit @code{int}; numbers for 16-bit @code{int} and 32-bit @code{int}; therefore I have
therefore I have indicated below the customary size (and other format indicated below the customary size (and other format information) for
information) for each type. The information below is currently correct each type. The information below is currently correct because AIX on
because AIX on the RS6000 is the only system which uses these type the RS6000 is the only system which uses these type numbers. If these
numbers. If these type numbers start to get used on other systems, I type numbers start to get used on other systems, I suspect the correct
suspect the correct thing to do is to define a new number in cases where thing to do is to define a new number in cases where a type does not
a type does not have the size and format indicated below. 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 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 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. @code{logical*4}, 32 bit unsigned integral type.
@item -24 @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 @item -25
@code{complex}. A complex type consisting of two IEEE single-precision @code{complex}. A complex type consisting of two IEEE single-precision