This is the mail archive of the gcc-patches@gcc.gnu.org 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]

[patch 3.0.2] Fix typos in *.texi.


Hi,

Attached is a patch to fix typos in doc/*.texi.  Comitted as obvious.

Thanks,

Kazu Hirata

2001-10-09  Kazu Hirata  <kazu@hxi.com>

	* doc/cpp.texi: Fix typos.
	* doc/c-tree.texi: Likewise.
	* doc/extend.texi: Likewise.
	* doc/invoke.texi: Likewise.
	* doc/objc.texi: Likewise.

Index: cpp.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/cpp.texi,v
retrieving revision 1.2.2.10
diff -u -r1.2.2.10 cpp.texi
--- cpp.texi	2001/10/08 22:35:25	1.2.2.10
+++ cpp.texi	2001/10/09 13:25:19
@@ -32,7 +32,7 @@
 
 @macro covertexts
 This manual contains no Invariant Sections.  The Front-Cover Texts are
-(a) (see below), and the the Back-Cover Texts are (b) (see below).
+(a) (see below), and the Back-Cover Texts are (b) (see below).
 
 (a) The FSF's Front-Cover Text is:
 
@@ -1950,7 +1950,7 @@
 to a single @samp{%}.
 
 @item __USER_LABEL_PREFIX__
-This macro expands to a single token which is the the prefix applied to
+This macro expands to a single token which is the prefix applied to
 user labels (symbols visible to C code) in assembly.  For example, in
 the @code{m68k-aout} environment it expands to an @samp{_}, but in the
 @code{m68k-coff} environment it expands to nothing.
@@ -3604,7 +3604,7 @@
 
 @cindex assertions, cancelling
 @findex #unassert
-Assertions can be cancelled with the the @samp{#unassert} directive.  It
+Assertions can be cancelled with the @samp{#unassert} directive.  It
 has the same syntax as @samp{#assert}.  In that form it cancels only the
 answer which was specified on the @samp{#unassert} line; other answers
 for that predicate remain true.  You can cancel an entire predicate by
Index: c-tree.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/c-tree.texi,v
retrieving revision 1.3.2.12
diff -u -r1.3.2.12 c-tree.texi
--- c-tree.texi	2001/10/07 11:07:17	1.3.2.12
+++ c-tree.texi	2001/10/09 13:25:19
@@ -1443,7 +1443,7 @@
 @item CASE_LABEL
 
 Use to represent a @code{case} label, range of @code{case} labels, or a
-@code{default} label.  If @code{CASE_LOW} is @code{NULL_TREE}, then this is a a
+@code{default} label.  If @code{CASE_LOW} is @code{NULL_TREE}, then this is a
 @code{default} label.  Otherwise, if @code{CASE_HIGH} is @code{NULL_TREE}, then
 this is an ordinary @code{case} label.  In this case, @code{CASE_LOW} is
 an expression giving the value of the label.  Both @code{CASE_LOW} and
@@ -1821,7 +1821,7 @@
 In general, the expression given above will overflow, so it should not
 be used to calculate the value of the constant.
 
-The variable @code{integer_zero_node} is a integer constant with value
+The variable @code{integer_zero_node} is an integer constant with value
 zero.  Similarly, @code{integer_one_node} is an integer constant with
 value one.  The @code{size_zero_node} and @code{size_one_node} variables
 are analogous, but have type @code{size_t} rather than @code{int}.
Index: extend.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/extend.texi,v
retrieving revision 1.1.2.14
diff -u -r1.1.2.14 extend.texi
--- extend.texi	2001/08/04 11:40:55	1.1.2.14
+++ extend.texi	2001/10/09 13:25:21
@@ -2150,7 +2150,7 @@
 enclosing declaration the type specifier appears in, and the type
 defined is not complete until after the attribute specifiers.
 @c Otherwise, there would be the following problems: a shift/reduce
-@c conflict between attributes binding the the struct/union/enum and
+@c conflict between attributes binding the struct/union/enum and
 @c binding to the list of specifiers/qualifiers; and "aligned"
 @c attributes could use sizeof for the structure, but the size could be
 @c changed later by "packed" attributes.
Index: invoke.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/invoke.texi,v
retrieving revision 1.3.2.25
diff -u -r1.3.2.25 invoke.texi
--- invoke.texi	2001/09/05 08:31:59	1.3.2.25
+++ invoke.texi	2001/10/09 13:25:23
@@ -1670,7 +1670,7 @@
 @item -fdiagnostics-show-location=every-line
 Only meaningful in line-wrapping mode.  Instructs the diagnostic
 messages reporter to emit the same source location information (as
-prefix) for physical lines that result from the process of breaking a
+prefix) for physical lines that result from the process of breaking
 a message which is too long to fit on a single line.
 
 @end table
@@ -3693,7 +3693,7 @@
 control some of these constants on the command-line using the
 @option{--param} option.
 
-In each case, the @var{value} is a integer.  The allowable choices for
+In each case, the @var{value} is an integer.  The allowable choices for
 @var{name} are given in the following table:
 
 @table @gcctabopt
Index: objc.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/objc.texi,v
retrieving revision 1.1.2.4
diff -u -r1.1.2.4 objc.texi
--- objc.texi	2001/06/26 22:51:19	1.1.2.4
+++ objc.texi	2001/10/09 13:25:23
@@ -251,7 +251,7 @@
 @end multitable
 
 Here are some types and their encodings, as they are generated by the
-compiler on a i386 machine:
+compiler on an i386 machine:
 
 @sp 1
 


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