OpenE2K
/
gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

extend.texi: Use lowercase "boolean". 

* doc/extend.texi: Use lowercase "boolean".
	* doc/invoke.texi: Likewise.
	* doc/md.texi: Likewise.
	* target.def: Likewise.
	* doc/tm.texi: Regenerated.

From-SVN: r240091
This commit is contained in:
Marek Polacek 2016-09-12 11:43:21 +00:00 committed by Marek Polacek
parent 684211e11b
commit 527a375057
6 changed files with 17 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
gcc/ChangeLog
View File

@ -1,3 +1,11 @@
2016-09-12 Marek Polacek <polacek@redhat.com>
* doc/extend.texi: Use lowercase "boolean".
* doc/invoke.texi: Likewise.
* doc/md.texi: Likewise.
* target.def: Likewise.
* doc/tm.texi: Regenerated.
2016-09-12 Kyrylo Tkachov <kyrylo.tkachov@arm.com>
PR middle-end/77426

8
gcc/doc/extend.texi
View File

@ -9486,7 +9486,7 @@ the pointer points.
@end smallexample
The object pointed to by the first argument must be of integer or pointer
type. It must not be a Boolean type.
type. It must not be a boolean type.
@emph{Note:} GCC 4.4 and later implement @code{__sync_fetch_and_nand}
as @code{*ptr = ~(tmp & value)} instead of @code{*ptr = ~tmp & value}.
@ -9772,7 +9772,7 @@ they are not scaled by the size of the type to which the pointer points.
@end smallexample
The object pointed to by the first argument must be of integer or pointer
type. It must not be a Boolean type. All memory orders are valid.
type. It must not be a boolean type. All memory orders are valid.
@end deftypefn
@ -9896,7 +9896,7 @@ behavior for all argument values.
The first built-in function allows arbitrary integral types for operands and
the result type must be pointer to some integral type other than enumerated or
Boolean type, the rest of the built-in functions have explicit integer types.
boolean type, the rest of the built-in functions have explicit integer types.
The compiler will attempt to use hardware instructions to implement
these built-in functions where possible, like conditional jump on overflow
@ -9942,7 +9942,7 @@ These built-in functions are similar to @code{__builtin_add_overflow},
@code{__builtin_sub_overflow}, or @code{__builtin_mul_overflow}, except that
they don't store the result of the arithmetic operation anywhere and the
last argument is not a pointer, but some expression with integral type other
than enumerated or Boolean type.
than enumerated or boolean type.
The built-in functions promote the first two operands into infinite precision signed type
and perform addition on those promoted operands. The result is then

2
gcc/doc/invoke.texi
View File

@ -5497,7 +5497,7 @@ if (a < 0 && a < 0) @{ @dots{} @}
@opindex Wlogical-not-parentheses
@opindex Wno-logical-not-parentheses
Warn about logical not used on the left hand side operand of a comparison.
This option does not warn if the right operand is considered to be a Boolean
This option does not warn if the right operand is considered to be a boolean
expression. Its purpose is to detect suspicious code like the following:
@smallexample
int a;

4
gcc/doc/md.texi
View File

@ -700,7 +700,7 @@ predicates used with @code{match_operand} have names that end in
@samp{_operand}, and those used with @code{match_operator} have names
that end in @samp{_operator}.
All predicates are Boolean functions (in the mathematical sense) of
All predicates are boolean functions (in the mathematical sense) of
two arguments: the RTL expression that is being considered at that
position in the instruction pattern, and the machine mode that the
@code{match_operand} or @code{match_operator} specifies. In this
@ -4274,7 +4274,7 @@ constraint. Docstrings are explained further below.
@end deffn
Non-register constraints are more like predicates: the constraint
definition gives a Boolean expression which indicates whether the
definition gives a boolean expression which indicates whether the
constraint matches.
@deffn {MD Expression} define_constraint name docstring exp

2
gcc/doc/tm.texi
View File

@ -1891,7 +1891,7 @@ This hook may conditionally modify five variables
@code{fixed_regs}, @code{call_used_regs}, @code{global_regs},
@code{reg_names}, and @code{reg_class_contents}, to take into account
any dependence of these register sets on target flags. The first three
of these are of type @code{char []} (interpreted as Boolean vectors).
of these are of type @code{char []} (interpreted as boolean vectors).
@code{global_regs} is a @code{const char *[]}, and
@code{reg_class_contents} is a @code{HARD_REG_SET}. Before the macro is
called, @code{fixed_regs}, @code{call_used_regs},

2
gcc/target.def
View File

@ -5340,7 +5340,7 @@ DEFHOOK
@code{fixed_regs}, @code{call_used_regs}, @code{global_regs},\n\
@code{reg_names}, and @code{reg_class_contents}, to take into account\n\
any dependence of these register sets on target flags. The first three\n\
of these are of type @code{char []} (interpreted as Boolean vectors).\n\
of these are of type @code{char []} (interpreted as boolean vectors).\n\
@code{global_regs} is a @code{const char *[]}, and\n\
@code{reg_class_contents} is a @code{HARD_REG_SET}. Before the macro is\n\
called, @code{fixed_regs}, @code{call_used_regs},\n\