Misc. Grammar Corrections

["Tom Browder" <tom dot browder at gmail dot com>]

Gerald Pfeifer suggests these proposed changes be considered by
others.  They are grammar changes I believe should be made for good
English usage.

The suggestion for an additional comma in the list may be
controversial for some modern (read "young") English authors.  I don't
know if there is a preferred GCC document usage, but Strunk and White,
a venerable US English style guide, prefers a comma after all items in
a list.


ChangeLog
==========

2008-02-03 Tom Browder <tom.browder@gmail.com>

	   * doc/passes.texi (Parsing pass): Inserted a hyphen to make
	     'language specific' a compound adjective (two instances of this
	     change).

	   (Tree-SSA passes): Used a comma to separate items in a series.

	   (Tree-SSA passes): Inserted two hyphens to make 'one to one' a
	   compound adjective.

	   * doc/c-tree.texi (Adding new DECL node types): Inserted a hyphen
	     to make 'language specific' a compound adjective
	   (four instances of this change).

	   * doc/install.texi (Downloading the source, Configuration,
	     Prerequisites, Installing GCC): Inserted a hyphen to make
	     'language specific' a compound adjective (two instances of this
	     change).

patch =============>
Index: passes.texi
===================================================================
--- passes.texi	(revision 132087)
+++ passes.texi	(working copy)
@@ -32,6 +32,6 @@
 @code{lang_hooks.parse_file}, to parse the entire input.  The language
 front end may use any intermediate language representation deemed
 appropriate.  The C front end uses GENERIC trees (CROSSREF), plus
-a double handful of language specific tree codes defined in
+a double handful of language-specific tree codes defined in
 @file{c-common.def}.  The Fortran front end uses a completely different
 private representation.

@@ -132,1 +132,1 @@
 invoke the @code{lang_hooks.gimplify_expr} callback.

 The callback should examine the expression in question and return
-@code{GS_UNHANDLED} if the expression is not a language specific
+@code{GS_UNHANDLED} if the expression is not a language-specific
 construct that requires attention.  Otherwise it should alter the
 expression in some way to such that forward progress is made toward
 producing valid GIMPLE@.  If the callback is certain that the
@@ -444,1 +444,1 @@
 @item Tree level if-conversion for vectorizer

 This pass applies if-conversion to simple loops to help vectorizer.
-We identify if convertible loops, if-convert statements and merge
+We identify if convertible loops, if-convert statements, and merge
 basic blocks in one big block.  The idea is to present loop in such
-form so that vectorizer can have one to one mapping between statements
+form so that vectorizer can have one-to-one mapping between statements
 and available vector operations.  This patch re-introduces COND_EXPR
 at GIMPLE level.  This pass is located in @file{tree-if-conv.c} and is
 described by @code{pass_if_conversion}.
Index: c-tree.texi
===================================================================
--- c-tree.texi	(revision 132087)
+++ c-tree.texi	(working copy)
@@ -1149,1 +1149,1 @@
 @table @asis

 @item Add a new tree code for the @code{DECL} node
-For language specific @code{DECL} nodes, there is a @file{.def} file
+For language-specific @code{DECL} nodes, there is a @file{.def} file
 in each frontend directory where the tree code should be added.
 For @code{DECL} nodes that are part of the middle-end, the code should
 be added to @file{tree.def}.
@@ -1168,2 +1168,2 @@
 Would create a structure name @code{tree_foo_decl} that inherits from
 @code{struct tree_decl_with_vis}.

-For language specific @code{DECL} nodes, this new structure type
+For language-specific @code{DECL} nodes, this new structure type
 should go in the appropriate @file{.h} file.
 For @code{DECL} nodes that are part of the middle-end, the structure
 type should go in @file{tree.h}.
@@ -1177,7 +1177,7 @@
 For garbage collection and dynamic checking purposes, each @code{DECL}
 node structure type is required to have a unique enumerator value
 specified with it.
-For language specific @code{DECL} nodes, this new enumerator value
+For language-specific @code{DECL} nodes, this new enumerator value
 should go in the appropriate @file{.def} file.
 For @code{DECL} nodes that are part of the middle-end, the enumerator
 values are specified in @file{treestruct.def}.
@@ -1185,7 +1185,7 @@
 @item Update @code{union tree_node}
 In order to make your new structure type usable, it must be added to
 @code{union tree_node}.
-For language specific @code{DECL} nodes, a new entry should be added
+For language-specific @code{DECL} nodes, a new entry should be added
 to the appropriate @file{.h} file of the form
 @smallexample
   struct tree_foo_decl GTY ((tag ("TS_VAR_DECL"))) foo_decl;
@@ -1202,2 +1202,2 @@
 hierarchy, or else checking and containment macros will fail
 inappropriately.

-For language specific @code{DECL} nodes, their is an @code{init_ts}
+For language-specific @code{DECL} nodes, there is an @code{init_ts}
 function in an appropriate @file{.c} file, which initializes the lookup
 table.
 Code setting up the table for new @code{DECL} nodes should be added
Index: install.texi
===================================================================
--- install.texi	(revision 132087)
+++ install.texi	(working copy)
@@ -483,1 +483,1 @@
 testsuites are also included in the full distribution.

 If you choose to download specific components, you must download the core
-GCC distribution plus any language specific distributions you wish to
+GCC distribution plus any language-specific distributions you wish to
 use.  The core distribution includes the C language front end as well as the
 shared components.  Each language has a tarball which includes the language
 front end as well as the language runtime (when appropriate).

-Unpack the core distribution as well as any language specific
+Unpack the core distribution as well as any language-specific
 distributions in the same directory.

 If you also intend to build binutils (either to upgrade an existing
<============= patch

-Tom