+Mon Jan 3 17:23:07 1994 Jim Kingdon (kingdon@lioth.cygnus.com)
+
+ * stabs.texinfo (String Field): Talk about defining several type
+ numbers at once.
+ Fix lint regarding changing node ELF Transformations to
+ ELF and SOM Transformations.
+
Fri Dec 31 00:42:43 1993 John Gilmore (gnu@cygnus.com)
* stabs.texinfo: Insert Peter Kessler's name as inventor (I think).
The @samp{@var{type-number}=} form is a type definition, where the
number represents a new type which is about to be defined. The type
definition may refer to other types by number, and those type numbers
-may be followed by @samp{=} and nested definitions.
+may be followed by @samp{=} and nested definitions. Also, the Lucid
+compiler will repeat @samp{@var{type-number}=} more than once if it
+wants to define several type numbers at once.
In a type definition, if the character that follows the equals sign is
non-numeric then it is a @var{type-descriptor}, and tells what kind of
@menu
* Transformations On Static Variables::
* Transformations On Global Variables::
-* ELF Transformations:: In ELF, things are a bit different.
+* ELF and SOM Transformations:: In ELF, things are a bit different.
@end menu
@node Transformations On Static Variables
@code{Bbss.bss} for the bss section, @code{Ddata.data} for the data
section, and @code{Drodata.rodata} for the rodata section. For the text
section, there is no such symbol (but there should be, see below). For
-an example of how these symbols work, @xref{ELF Transformations}. GCC
+an example of how these symbols work, @xref{ELF and SOM Transformations}. GCC
does not provide these symbols; it instead relies on the stabs getting
relocated. Thus addresses which would normally be relative to
@code{Bbss.bss}, etc., are already relocated. The Sun linker provided