Patch to use "nonzero" consistently in GCC manual
Joseph S. Myers
jsm28@cam.ac.uk
Tue Oct 9 16:16:00 GMT 2001
This patch changes "non-zero" to "nonzero" in the GCC manual. It
passes "make info" and "make dvi". Applied to mainline and (those
parts that apply there) to 3.0 branch.
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".
diff -ruN doc.orig/c-tree.texi doc/c-tree.texi
--- doc.orig/c-tree.texi Tue Oct 9 07:59:35 2001
+++ doc/c-tree.texi Tue Oct 9 22:56:27 2001
@@ -110,7 +110,7 @@
@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 @@
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 @@
@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 @@
@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
diff -ruN doc.orig/cppinternals.texi doc/cppinternals.texi
--- doc.orig/cppinternals.texi Sat Oct 6 11:54:54 2001
+++ doc/cppinternals.texi Tue Oct 9 22:56:27 2001
@@ -203,7 +203,7 @@
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
diff -ruN doc.orig/extend.texi doc/extend.texi
--- doc.orig/extend.texi Tue Oct 9 07:59:35 2001
+++ doc/extend.texi Tue Oct 9 22:56:27 2001
@@ -4121,7 +4121,7 @@
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 @@
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
diff -ruN doc.orig/install.texi doc/install.texi
--- doc.orig/install.texi Wed Sep 26 00:08:56 2001
+++ doc/install.texi Tue Oct 9 22:56:27 2001
@@ -772,7 +772,7 @@
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.
diff -ruN doc.orig/md.texi doc/md.texi
--- doc.orig/md.texi Fri Aug 31 10:16:46 2001
+++ doc/md.texi Tue Oct 9 22:56:27 2001
@@ -2569,11 +2569,11 @@
@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 @@
@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 @@
@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 @@
@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 @@
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 @@
@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 @@
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).
diff -ruN doc.orig/rtl.texi doc/rtl.texi
--- doc.orig/rtl.texi Wed Sep 5 07:47:55 2001
+++ doc/rtl.texi Tue Oct 9 22:56:27 2001
@@ -1776,8 +1776,8 @@
@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 @@
@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.
diff -ruN doc.orig/tm.texi doc/tm.texi
--- doc.orig/tm.texi Tue Oct 9 07:59:35 2001
+++ doc/tm.texi Tue Oct 9 22:56:27 2001
@@ -124,7 +124,7 @@
@item SWITCH_CURTAILS_COMPILATION (@var{char})
A C expression which determines whether the option @option{-@var{char}}
stops compilation before the generation of an executable. The value is
-boolean, non-zero if the option does stop an executable from being
+boolean, nonzero if the option does stop an executable from being
generated, zero otherwise.
By default, this macro is defined as
@@ -779,7 +779,7 @@
@var{level} is the optimization level specified; 2 if @option{-O2} is
specified, 1 if @option{-O} is specified, and 0 if neither is specified.
-@var{size} is non-zero if @option{-Os} is specified and zero otherwise.
+@var{size} is nonzero if @option{-Os} is specified and zero otherwise.
You should not use this macro to change options that are not
machine-specific. These should uniformly selected by the same
@@ -1737,7 +1737,7 @@
@cindex call-used register
@cindex call-clobbered register
@cindex call-saved register
-A C expression that is non-zero if it is not permissible to store a
+A C expression that is nonzero if it is not permissible to store a
value of mode @var{mode} in hard register number @var{regno} across a
call without some part of it being clobbered. For most machines this
macro need not be defined. It is only required for machines that do not
@@ -2357,7 +2357,7 @@
@item SECONDARY_MEMORY_NEEDED (@var{class1}, @var{class2}, @var{m})
Certain machines have the property that some registers cannot be copied
to some other registers without using memory. Define this macro on
-those machines to be a C expression that is non-zero if objects of mode
+those machines to be a C expression that is nonzero if objects of mode
@var{m} in registers of @var{class1} can only be copied to registers of
class @var{class2} by storing a register of @var{class1} into memory
and loading that memory location into a register of @var{class2}.
@@ -2406,14 +2406,14 @@
if the required hard register is used for another purpose across such an
insn.
-Define @code{SMALL_REGISTER_CLASSES} to be an expression with a non-zero
-value on these machines. When this macro has a non-zero value, the
+Define @code{SMALL_REGISTER_CLASSES} to be an expression with a nonzero
+value on these machines. When this macro has a nonzero value, the
compiler will try to minimize the lifetime of hard registers.
-It is always safe to define this macro with a non-zero value, but if you
+It is always safe to define this macro with a nonzero value, but if you
unnecessarily define it, you will reduce the amount of optimizations
that can be performed in some cases. If you do not define this macro
-with a non-zero value when it is required, the compiler will run out of
+with a nonzero value when it is required, the compiler will run out of
spill registers and print a fatal error message. For most machines, you
should not define this macro at all.
@@ -3077,7 +3077,7 @@
@findex CAN_ELIMINATE
@item CAN_ELIMINATE (@var{from-reg}, @var{to-reg})
-A C expression that returns non-zero if the compiler is allowed to try
+A C expression that returns nonzero if the compiler is allowed to try
to replace register number @var{from-reg} with register number
@var{to-reg}. This macro need only be defined if @code{ELIMINABLE_REGS}
is defined, and will usually be the constant 1, since most of the cases
@@ -3325,7 +3325,7 @@
You may use the macro @code{MUST_PASS_IN_STACK (@var{mode}, @var{type})}
in the definition of this macro to determine if this argument is of a
type that must be passed in the stack. If @code{REG_PARM_STACK_SPACE}
-is not defined and @code{FUNCTION_ARG} returns non-zero for such an
+is not defined and @code{FUNCTION_ARG} returns nonzero for such an
argument, the compiler will abort. If @code{REG_PARM_STACK_SPACE} is
defined, the argument will be computed in the stack and then loaded into
a register.
@@ -4730,14 +4730,14 @@
@itemx HAVE_PRE_DECREMENT
@itemx HAVE_POST_INCREMENT
@itemx HAVE_POST_DECREMENT
-A C expression that is non-zero if the machine supports pre-increment,
+A C expression that is nonzero if the machine supports pre-increment,
pre-decrement, post-increment, or post-decrement addressing respectively.
@findex HAVE_POST_MODIFY_DISP
@findex HAVE_PRE_MODIFY_DISP
@item HAVE_PRE_MODIFY_DISP
@itemx HAVE_POST_MODIFY_DISP
-A C expression that is non-zero if the machine supports pre- or
+A C expression that is nonzero if the machine supports pre- or
post-address side-effect generation involving constants other than
the size of the memory operand.
@@ -4745,7 +4745,7 @@
@findex HAVE_PRE_MODIFY_REG
@item HAVE_PRE_MODIFY_REG
@itemx HAVE_POST_MODIFY_REG
-A C expression that is non-zero if the machine supports pre- or
+A C expression that is nonzero if the machine supports pre- or
post-address side-effect generation involving a register displacement.
@findex CONSTANT_ADDRESS_P
@@ -5273,7 +5273,7 @@
@item MEMORY_MOVE_COST (@var{mode}, @var{class}, @var{in})
A C expression for the cost of moving data of mode @var{mode} between a
register of class @var{class} and memory; @var{in} is zero if the value
-is to be written to memory, non-zero if it is to be read in. This cost
+is to be written to memory, nonzero if it is to be read in. This cost
is relative to those in @code{REGISTER_MOVE_COST}. If moving between
registers and memory is more expensive than between two registers, you
should define this macro to express the relative cost.
@@ -5342,15 +5342,15 @@
than aligned accesses, for example if they are emulated in a trap
handler.
-When this macro is non-zero, the compiler will act as if
-@code{STRICT_ALIGNMENT} were non-zero when generating code for block
+When this macro is nonzero, the compiler will act as if
+@code{STRICT_ALIGNMENT} were nonzero when generating code for block
moves. This can cause significantly more instructions to be produced.
-Therefore, do not set this macro non-zero if unaligned accesses only add a
+Therefore, do not set this macro nonzero if unaligned accesses only add a
cycle or two to the time for a memory access.
If the value of this macro is always zero, it need not be defined. If
-this macro is defined, it should produce a non-zero value when
-@code{STRICT_ALIGNMENT} is non-zero.
+this macro is defined, it should produce a nonzero value when
+@code{STRICT_ALIGNMENT} is nonzero.
@findex DONT_REDUCE_ADDR
@item DONT_REDUCE_ADDR
@@ -5682,7 +5682,7 @@
@findex JUMP_TABLES_IN_TEXT_SECTION
@item JUMP_TABLES_IN_TEXT_SECTION
-Define this macro to be an expression with a non-zero value if jump
+Define this macro to be an expression with a nonzero value if jump
tables (for @code{tablejump} insns) should be output in the text
section, along with the assembler instructions. Otherwise, the
readonly data section is used.
@@ -5908,7 +5908,7 @@
Output assembly directives to switch to section @var{name}. The section
should have attributes as specified by @var{flags}, which is a bit mask
of the @code{SECTION_*} flags defined in @file{output.h}. If @var{align}
-is non-zero, it contains an alignment in bytes to be used for the section,
+is nonzero, it contains an alignment in bytes to be used for the section,
otherwise some target default should be used. Only targets that must
specify an alignment within the section directive need pay attention to
@var{align} -- we will still use @code{ASM_OUTPUT_ALIGN}.
@@ -6033,7 +6033,7 @@
@findex CONSTANT_POOL_BEFORE_FUNCTION
@item CONSTANT_POOL_BEFORE_FUNCTION
You may define this macro as a C expression. You should define the
-expression to have a non-zero value if GCC should output the constant
+expression to have a nonzero value if GCC should output the constant
pool for a function before the code for the function, or a zero value if
GCC should output the constant pool after the function. If you do
not define this macro, the usual case, GCC will output the constant
@@ -7994,7 +7994,7 @@
You can have multiple entities that are mode-switched, and select at run time
which entities actually need it. @code{OPTIMIZE_MODE_SWITCHING} should
-return non-zero for any @var{entity} that that needs mode-switching.
+return nonzero for any @var{entity} that that needs mode-switching.
If you define this macro, you also have to define
@code{NUM_MODES_FOR_MODE_SWITCHING}, @code{MODE_NEEDED},
@code{MODE_PRIORITY_TO_MODE} and @code{EMIT_MODE_SET}.
@@ -8275,7 +8275,7 @@
A C expression that is nonzero if on this machine the number of bits
actually used for the count of a shift operation is equal to the number
of bits needed to represent the size of the object being shifted. When
-this macro is non-zero, the compiler will assume that it is safe to omit
+this macro is nonzero, the compiler will assume that it is safe to omit
a sign-extend, zero-extend, and certain bitwise `and' instructions that
truncates the count of a shift operation. On machines that have
instructions that act on bit-fields at variable positions, which may
@@ -8416,7 +8416,7 @@
@findex FLOAT_STORE_FLAG_VALUE
@item FLOAT_STORE_FLAG_VALUE (@var{mode})
-A C expression that gives a non-zero @code{REAL_VALUE_TYPE} value that is
+A C expression that gives a nonzero @code{REAL_VALUE_TYPE} value that is
returned when comparison operators with floating-point results are true.
Define this macro on machine that have comparison operations that return
floating-point values. If there are no such operations, do not define
--
Joseph S. Myers
jsm28@cam.ac.uk
More information about the Gcc-patches
mailing list