c-tree.texi, [...]: Consistently use "nonzero" instead of "non-zero".

	* doc/c-tree.texi, doc/cppinternals.texi, doc/extend.texi,
	doc/install.texi, doc/md.texi, doc/rtl.texi, doc/tm.texi:
	Consistently use "nonzero" instead of "non-zero".

From-SVN: r46134

gcc/ChangeLog

+2001-10-10  Joseph S. Myers  <jsm28@cam.ac.uk>
+
+	* doc/c-tree.texi, doc/cppinternals.texi, doc/extend.texi,
+	doc/install.texi, doc/md.texi, doc/rtl.texi, doc/tm.texi:
+	Consistently use "nonzero" instead of "non-zero".
+
 2001-10-09  Kazu Hirata  <kazu@hxi.com>
 
 	* acconfig.h: Fix comment formatting.

gcc/doc/c-tree.texi

@@ -110,7 +110,7 @@ int i = (TEST_P (t) != 0);
 @noindent
 are legal.  Macros that return @code{int} values now may be changed to
 return @code{tree} values, or other pointers in the future.  Even those
-that continue to return @code{int} may return multiple non-zero codes
+that continue to return @code{int} may return multiple nonzero codes
 where previously they returned only zero and one.  Therefore, you should
 not write code like
 @example
@@ -1183,7 +1183,7 @@ returning to the thunk.  The first parameter to the thunk is always the
 value.  (The @code{THUNK_DELTA} is an @code{int}, not an
 @code{INTEGER_CST}.)
 
-Then, if @code{THUNK_VCALL_OFFSET} (an @code{INTEGER_CST}) is non-zero
+Then, if @code{THUNK_VCALL_OFFSET} (an @code{INTEGER_CST}) is nonzero
 the adjusted @code{this} pointer must be adjusted again.  The complete
 calculation is given by the following pseudo-code:
 
@@ -2087,7 +2087,7 @@ the value of the second operand.
 
 @item COND_EXPR
 These nodes represent @code{?:} expressions.  The first operand
-is of boolean or integral type.  If it evaluates to a non-zero value,
+is of boolean or integral type.  If it evaluates to a nonzero value,
 the second operand should be evaluated, and returned as the value of the
 expression.  Otherwise, the third operand is evaluated, and returned as
 the value of the expression.  As a GNU extension, the middle operand of
@@ -2165,7 +2165,7 @@ an @code{EXIT_EXPR} is encountered.
 @item EXIT_EXPR
 These nodes represent conditional exits from the nearest enclosing
 @code{LOOP_EXPR}.  The single operand is the condition; if it is
-non-zero, then the loop should be exited.  An @code{EXIT_EXPR} will only
+nonzero, then the loop should be exited.  An @code{EXIT_EXPR} will only
 appear within a @code{LOOP_EXPR}.
 
 @item CLEANUP_POINT_EXPR

gcc/doc/cppinternals.texi

@@ -203,7 +203,7 @@ error about an unterminated macro argument list.
 The C standard also specifies that a new line in the middle of the
 arguments to a macro is treated as whitespace.  This white space is
 important in case the macro argument is stringified.  The state variable
-@code{parsing_args} is non-zero when the preprocessor is collecting the
+@code{parsing_args} is nonzero when the preprocessor is collecting the
 arguments to a macro call.  It is set to 1 when looking for the opening
 parenthesis to a function-like macro, and 2 when collecting the actual
 arguments up to the closing parenthesis, since these two cases need to

gcc/doc/extend.texi

@@ -4121,7 +4121,7 @@ of the stack has been reached, this function will return @code{0} or a
 random value. In addition, @code{__builtin_frame_address} may be used
 to determine if the top of the stack has been reached.
 
-This function should only be used with a non-zero argument for debugging
+This function should only be used with a nonzero argument for debugging
 purposes.
 @end deftypefn
 
@@ -4146,7 +4146,7 @@ any function other than the current one; in such cases, or when the top
 of the stack has been reached, this function will return @code{0} if
 the first frame pointer is properly initialized by the startup code.
 
-This function should only be used with a non-zero argument for debugging
+This function should only be used with a nonzero argument for debugging
 purposes.
 @end deftypefn
 

gcc/doc/install.texi

@@ -772,7 +772,7 @@ Other broken versions may recompile parts of the compiler when
 installing the compiler.)
 
 Some commands executed when making the compiler may fail (return a
-non-zero status) and be ignored by @code{make}.  These failures, which
+nonzero status) and be ignored by @code{make}.  These failures, which
 are often due to files that were not found, are expected, and can safely
 be ignored.
 

gcc/doc/md.texi

@@ -2569,11 +2569,11 @@ insn.
 @cindex @code{call_value_pop} instruction pattern
 @item @samp{call_pop}, @samp{call_value_pop}
 Similar to @samp{call} and @samp{call_value}, except used if defined and
-if @code{RETURN_POPS_ARGS} is non-zero.  They should emit a @code{parallel}
+if @code{RETURN_POPS_ARGS} is nonzero.  They should emit a @code{parallel}
 that contains both the function call and a @code{set} to indicate the
 adjustment made to the frame pointer.
 
-For machines where @code{RETURN_POPS_ARGS} can be non-zero, the use of these
+For machines where @code{RETURN_POPS_ARGS} can be nonzero, the use of these
 patterns increases the number of functions for which the frame pointer
 can be eliminated, if desired.
 
@@ -2608,7 +2608,7 @@ to save any registers or allocate stack space.
 @findex reload_completed
 @findex leaf_function_p
 For such machines, the condition specified in this pattern should only
-be true when @code{reload_completed} is non-zero and the function's
+be true when @code{reload_completed} is nonzero and the function's
 epilogue would only be a single instruction.  For machines with register
 windows, the routine @code{leaf_function_p} may be used to determine if
 a register window push is required.
@@ -2707,9 +2707,9 @@ that the jump optimizer will not delete the table as unreachable code.
 @cindex @code{decrement_and_branch_until_zero} instruction pattern
 @item @samp{decrement_and_branch_until_zero}
 Conditional branch instruction that decrements a register and
-jumps if the register is non-zero.  Operand 0 is the register to
+jumps if the register is nonzero.  Operand 0 is the register to
 decrement and test; operand 1 is the label to jump to if the
-register is non-zero.  @xref{Looping Patterns}.
+register is nonzero.  @xref{Looping Patterns}.
 
 This optional instruction pattern is only used by the combiner,
 typically for loops reversed by the loop optimizer when strength
@@ -2718,13 +2718,13 @@ reduction is enabled.
 @cindex @code{doloop_end} instruction pattern
 @item @samp{doloop_end}
 Conditional branch instruction that decrements a register and jumps if
-the register is non-zero.  This instruction takes five operands: Operand
+the register is nonzero.  This instruction takes five operands: Operand
 0 is the register to decrement and test; operand 1 is the number of loop
 iterations as a @code{const_int} or @code{const0_rtx} if this cannot be
 determined until run-time; operand 2 is the actual or estimated maximum
 number of iterations as a @code{const_int}; operand 3 is the number of
 enclosed loops as a @code{const_int} (an innermost loop has a value of
-1); operand 4 is the label to jump to if the register is non-zero.
+1); operand 4 is the label to jump to if the register is nonzero.
 @xref{Looping Patterns}.
 
 This optional instruction pattern should be defined for machines with
@@ -3734,10 +3734,10 @@ Patterns are matched against @var{insn-pattern} in two different
 circumstances.  If an insn needs to be split for delay slot scheduling
 or insn scheduling, the insn is already known to be valid, which means
 that it must have been matched by some @code{define_insn} and, if
-@code{reload_completed} is non-zero, is known to satisfy the constraints
+@code{reload_completed} is nonzero, is known to satisfy the constraints
 of that @code{define_insn}.  In that case, the new insn patterns must
 also be insns that are matched by some @code{define_insn} and, if
-@code{reload_completed} is non-zero, must also satisfy the constraints
+@code{reload_completed} is nonzero, must also satisfy the constraints
 of those definitions.
 
 As an example of this usage of @code{define_split}, consider the following
@@ -4348,7 +4348,7 @@ expression is that of the @var{default} expression.
 @table @code
 @cindex @code{const_int} and attribute tests
 @item (const_int @var{i})
-This test is true if @var{i} is non-zero and false otherwise.
+This test is true if @var{i} is nonzero and false otherwise.
 
 @cindex @code{not} and attributes
 @cindex @code{ior} and attributes
@@ -4363,7 +4363,7 @@ These tests are true if the indicated logical function is true.
 This test is true if operand @var{n} of the insn whose attribute value
 is being determined has mode @var{m} (this part of the test is ignored
 if @var{m} is @code{VOIDmode}) and the function specified by the string
-@var{pred} returns a non-zero value when passed operand @var{n} and mode
+@var{pred} returns a nonzero value when passed operand @var{n} and mode
 @var{m} (this part of the test is ignored if @var{pred} is the null
 string).
 

gcc/doc/rtl.texi

@@ -1776,8 +1776,8 @@ to express conditional jumps.
 @item (cond [@var{test1} @var{value1} @var{test2} @var{value2} @dots{}] @var{default})
 Similar to @code{if_then_else}, but more general.  Each of @var{test1},
 @var{test2}, @dots{} is performed in turn.  The result of this expression is
-the @var{value} corresponding to the first non-zero test, or @var{default} if
-none of the tests are non-zero expressions.
+the @var{value} corresponding to the first nonzero test, or @var{default} if
+none of the tests are nonzero expressions.
 
 This is currently not valid for instruction patterns and is supported only
 for insn attributes.  @xref{Insn Attributes}.
@@ -2256,7 +2256,7 @@ any, must deal with such insns if you define any peephole optimizations.
 @findex cond_exec
 @item (cond_exec [@var{cond} @var{expr}])
 Represents a conditionally executed expression.  The @var{expr} is
-executed only if the @var{cond} is non-zero.  The @var{cond} expression
+executed only if the @var{cond} is nonzero.  The @var{cond} expression
 must not have side-effects, but the @var{expr} may very well have
 side-effects.