This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Doc fixes

Here are fixes for a few formatting glitches in the texinfo docs.

1999-03-18  Andreas Schwab  <>

	* invoke.texi: Fix use of @item vs @itemx.

	* tm.texi (Varargs): Don't split argument of @item across lines.

--- egcs-2.93/gcc/invoke.texi.~1~	Mon Mar  1 20:44:40 1999
+++ egcs-2.93/gcc/invoke.texi	Mon Mar  1 22:22:52 1999
@@ -2369,7 +2369,7 @@
 Perform a number of minor optimizations that are relatively expensive.
 @item -foptimize-register-moves
-@item -fregmove
+@itemx -fregmove
 Attempt to reassign register numbers in move instructions and as
 operands of other simple instructions in order to maximize the amount of
 register tying.  This is especially helpful on machines with two-operand
@@ -2398,7 +2398,7 @@
 registers and where memory load instructions take more than one cycle.
 @item -ffunction-sections
-@item -fdata-sections
+@itemx -fdata-sections
 Place each function or data item into its own section in the output
 file if the target supports arbitrary sections.  The name of the
 function or the name of the data item determines the section's name
@@ -3803,7 +3803,7 @@
 compiler is built for cross-compilation.
 @item -mcpu=<name>
-@item -mtune=<name>
+@itemx -mtune=<name>
 @kindex -mcpu=
 @kindex -mtune=
 This specifies the name of the target ARM processor.  GCC uses this name
@@ -3824,7 +3824,7 @@
 armv3, armv3m, armv4, armv4t
 @item -mfpe=<number>
-@item -mfp=<number>
+@itemx -mfp=<number>
 @kindex -mfpe=
 @kindex -mfp=
 This specifes the version of the floating point emulation available on
@@ -5722,8 +5722,8 @@
 All variants support @samp{-mcpu=base}, this is the default.
 @item -mtext=@var{text section}
-@item -mdata=@var{data section}
-@item -mrodata=@var{readonly data section}
+@itemx -mdata=@var{data section}
+@itemx -mrodata=@var{readonly data section}
 Put functions, data, and readonly data in @var{text section},
 @var{data section}, and @var{readonly data section} respectively
 by default.  This can be overridden with the @code{section} attribute.
--- egcs-2.93/gcc/tm.texi.~1~	Mon Mar  1 20:45:53 1999
+++ egcs-2.93/gcc/tm.texi	Mon Mar  1 22:40:57 1999
@@ -3739,11 +3739,8 @@
 If this macro is not defined, the compiler will output an ordinary
 call to the library function @samp{__builtin_saveregs}.
-@c !!! a bug in texinfo; how to make the entry on the @item line allow
-@c more than one line of text... help...  --mew 10feb93
-@item SETUP_INCOMING_VARARGS (@var{args_so_far}, @var{mode}, @var{type},
-@var{pretend_args_size}, @var{second_time})
+@item SETUP_INCOMING_VARARGS (@var{args_so_far}, @var{mode}, @var{type}, @var{pretend_args_size}, @var{second_time})
 This macro offers an alternative to using @code{__builtin_saveregs} and
 defining the macro @code{EXPAND_BUILTIN_SAVEREGS}.  Use it to store the
 anonymous register arguments into the stack so that all the arguments

Andreas Schwab                                      "And now for something                      completely different"

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]