Texinfo trivia

Dave Love d.love@dl.ac.uk
Fri Feb 26 11:36:00 GMT 1999

These barf with the prerelease makeinfo like the g77 cases [that I
thought we'd fixed previously...].

Fri Feb 26 19:31:25 1999  Dave Love  <fx@gnu.org>

	* md.texi, invoke.texi: Fix unterminated @xrefs.

Index: invoke.texi
RCS file: /egcs/carton/cvsfiles/egcs/gcc/invoke.texi,v
retrieving revision 1.94
diff -u -p -r1.94 invoke.texi
--- invoke.texi	1999/02/22 16:47:47	1.94
+++ invoke.texi	1999/02/26 19:31:24
@@ -5058,7 +5058,7 @@ there.
 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,8 @@ supported letters are: @code{a} allocate
 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 +5730,7 @@ All variants support @samp{-mcpu=base}, 
 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
Index: md.texi
RCS file: /egcs/carton/cvsfiles/egcs/gcc/md.texi,v
retrieving revision 1.23
diff -u -p -r1.23 md.texi
--- md.texi	1999/02/21 18:39:33	1.23
+++ md.texi	1999/02/26 19:31:26
@@ -2181,7 +2181,7 @@ pattern or a @samp{tst@var{m}} pattern.
 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.

More information about the Gcc-patches mailing list