Fixes for texinfo files

Andreas Jaeger aj@arthur.rhein-neckar.de
Thu Feb 25 00:28:00 GMT 1999


The current egcs mainstream runs my installed makeinfo instead of the
one that comes with egcs (this has been discussed already on the egcs
list).  The problem is that the installed makeinfo version (3.12d)
reports four errors:

makeinfo  -I../../egcs-cvs/gcc -o gcc.info ../../egcs-cvs/gcc/gcc.texi
../../egcs-cvs/gcc/invoke.texi:5061: `.' or `,' must follow cross reference, not @.
../../egcs-cvs/gcc/invoke.texi:5087: `.' or `,' must follow cross reference, not @.
../../egcs-cvs/gcc/invoke.texi:5732: `.' or `,' must follow cross reference, not @.
../../egcs-cvs/gcc/md.texi:2184: `.' or `,' must follow cross reference, not T.
makeinfo: Removing output file `gcc.info' due to errors; use --force to preserve
.
make[2]: *** [gcc.info] Error 2

I'm appending a patch for this.
Andreas

1999-02-25  Andreas Jaeger  <aj@arthur.rhein-neckar.de>

	* invoke.texi: Add missing `.' after cross references.
	* md.texi (Standard Names): Likewise.

--- gcc/invoke.texi.~1~	Tue Feb 23 13:40:04 1999
+++ gcc/invoke.texi	Thu Feb 25 08:58:45 1999
@@ -5058,7 +5058,7 @@
 You can specify that an individual function is called with this calling
 sequence with the function attribute @samp{stdcall}.  You can also
 override the @samp{-mrtd} option by using the function attribute
-@samp{cdecl}. @xref{Function Attributes}
+@samp{cdecl}. @xref{Function Attributes}.
 
 @strong{Warning:} this calling convention is incompatible with the one
 normally used on Unix, so you cannot use it if you need to call
@@ -5084,7 +5084,7 @@
 Control how many registers are used to pass integer arguments.  By
 default, no registers are used to pass arguments, and at most 3
 registers can be used.  You can control this behavior for a specific
-function by using the function attribute @samp{regparm}.   @xref{Function Attributes}
+function by using the function attribute @samp{regparm}.   @xref{Function Attributes}.
 
 @strong{Warning:} if you use this switch, and
 @var{num} is nonzero, then you must build all modules with the same
@@ -5729,7 +5729,7 @@
 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.
-@xref{Variable Attributes}
+@xref{Variable Attributes}.
 
 @end table
 
--- gcc/md.texi.~1~	Mon Feb 22 07:57:58 1999
+++ gcc/md.texi	Thu Feb 25 08:59:25 1999
@@ -2181,7 +2181,7 @@
 
 Machines that use a pseudo register for the condition code value, or
 where the mode used for the comparison depends on the condition being
-tested, should also use the above mechanism.  @xref{Jump Patterns}
+tested, should also use the above mechanism.  @xref{Jump Patterns}.
 
 The above discussion also applies to the @samp{mov@var{mode}cc} and
 @samp{s@var{cond}} patterns.

-- 
 Andreas Jaeger   aj@arthur.rhein-neckar.de    jaeger@informatik.uni-kl.de
  for pgp-key finger ajaeger@aixd1.rhrk.uni-kl.de


More information about the Gcc-patches mailing list