sourcebuild.texi: Add comma for clarity.
* doc/sourcebuild.texi: Add comma for clarity. * doc/extend.texi: Fix some typos. * doc/passes.texi: Likewise. * doc/cppinternals.texi: Likewise. * doc/c-tree.texi: Likewise. * doc/tree-ssa.texi: Likewise. From-SVN: r121241
This commit is contained in:
parent
7fbb9a499c
commit
1eaf20ec87
|
@ -2193,7 +2193,7 @@ pointer or reference type.
|
|||
|
||||
@item FIX_TRUNC_EXPR
|
||||
These nodes represent conversion of a floating-point value to an
|
||||
integer. The single operand will have a floating-point type, while the
|
||||
integer. The single operand will have a floating-point type, while
|
||||
the complete expression will have an integral (or boolean) type. The
|
||||
operand is rounded towards zero.
|
||||
|
||||
|
|
|
@ -963,7 +963,7 @@ directives outside the main conditional block for the optimization to be
|
|||
on.
|
||||
|
||||
Note that whilst we are inside the conditional block, @code{mi_valid} is
|
||||
likely to be reset to @code{false}, but this does not matter since the
|
||||
likely to be reset to @code{false}, but this does not matter since
|
||||
the closing @code{#endif} restores it to @code{true} if appropriate.
|
||||
|
||||
Finally, since @code{_cpp_lex_direct} pops the file off the buffer stack
|
||||
|
|
|
@ -1290,7 +1290,7 @@ As a GNU extension, GCC allows initialization of objects with static storage
|
|||
duration by compound literals (which is not possible in ISO C99, because
|
||||
the initializer is not a constant).
|
||||
It is handled as if the object was initialized only with the bracket
|
||||
enclosed list if compound literal's and object types match.
|
||||
enclosed list if the types of the compound literal and the object match.
|
||||
The initializer list of the compound literal must be constant.
|
||||
If the object being initialized has array type of unknown size, the size is
|
||||
determined by compound literal size.
|
||||
|
@ -10123,7 +10123,7 @@ macros are defined.
|
|||
@cindex pragma, diagnostic
|
||||
|
||||
Modifies the disposition of a diagnostic. Note that not all
|
||||
diagnostics are modifyiable; at the moment only warnings (normally
|
||||
diagnostics are modifiable; at the moment only warnings (normally
|
||||
controlled by @samp{-W...}) can be controlled, and not all of them.
|
||||
Use @option{-fdiagnostics-show-option} to determine which diagnostics
|
||||
are controllable and which option controls them.
|
||||
|
@ -11151,7 +11151,7 @@ and are now removed from G++.
|
|||
The implicit typename extension has been deprecated and is now
|
||||
removed from G++.
|
||||
|
||||
The use of default arguments in function pointers, function typedefs and
|
||||
The use of default arguments in function pointers, function typedefs
|
||||
and other places where they are not permitted by the standard is
|
||||
deprecated and will be removed from a future version of G++.
|
||||
|
||||
|
|
|
@ -909,7 +909,7 @@ tools can not generate or interpret stabs.
|
|||
@item --disable-multilib
|
||||
Specify that multiple target
|
||||
libraries to support different target variants, calling
|
||||
conventions, etc should not be built. The default is to build a
|
||||
conventions, etc.@: should not be built. The default is to build a
|
||||
predefined set of them.
|
||||
|
||||
Some targets provide finer-grained control over which multilibs are built
|
||||
|
|
|
@ -223,7 +223,7 @@ library. The pass is located in @file{omp-low.c} and is described by
|
|||
|
||||
@item Lower control flow
|
||||
|
||||
This pass flattens @code{if} statements (@code{COND_EXPR}) and
|
||||
This pass flattens @code{if} statements (@code{COND_EXPR})
|
||||
and moves lexical bindings (@code{BIND_EXPR}) out of line. After
|
||||
this pass, all @code{if} statements will have exactly two @code{goto}
|
||||
statements in its @code{then} and @code{else} arms. Lexical binding
|
||||
|
@ -324,7 +324,7 @@ This pass performs a flow sensitive SSA-based points-to analysis.
|
|||
The resulting may-alias, must-alias, and escape analysis information
|
||||
is used to promote variables from in-memory addressable objects to
|
||||
non-aliased variables that can be renamed into SSA form. We also
|
||||
update the @code{VDEF}/@code{VUSE} memory tags for non-renamable
|
||||
update the @code{VDEF}/@code{VUSE} memory tags for non-renameable
|
||||
aggregates so that we get fewer false kills. The pass is located
|
||||
in @file{tree-ssa-alias.c} and is described by @code{pass_may_alias}.
|
||||
|
||||
|
|
|
@ -823,7 +823,7 @@ here; FIXME: document the others.
|
|||
@node Test Idioms
|
||||
@subsection Idioms Used in Testsuite Code
|
||||
|
||||
In general C testcases have a trailing @file{-@var{n}.c}, starting
|
||||
In general, C testcases have a trailing @file{-@var{n}.c}, starting
|
||||
with @file{-1.c}, in case other testcases with similar names are added
|
||||
later. If the test is a test of some well-defined feature, it should
|
||||
have a name referring to that feature such as
|
||||
|
|
|
@ -874,7 +874,7 @@ incorrect assumptions about them.
|
|||
Operands are updated as soon as the statement is finished via a call
|
||||
to @code{update_stmt}. If statement elements are changed via
|
||||
@code{SET_USE} or @code{SET_DEF}, then no further action is required
|
||||
(ie, those macros take care of updating the statement). If changes
|
||||
(i.e., those macros take care of updating the statement). If changes
|
||||
are made by manipulating the statement's tree directly, then a call
|
||||
must be made to @code{update_stmt} when complete. Calling one of the
|
||||
@code{bsi_insert} routines or @code{bsi_replace} performs an implicit
|
||||
|
@ -1109,9 +1109,9 @@ each stmt after that is done:
|
|||
@}
|
||||
@end smallexample
|
||||
|
||||
There are 2 iterators which can be used. @code{FOR_EACH_IMM_USE_FAST} is used
|
||||
when the immediate uses are not changed, ie. you are looking at the uses, but
|
||||
not setting them.
|
||||
There are 2 iterators which can be used. @code{FOR_EACH_IMM_USE_FAST} is
|
||||
used when the immediate uses are not changed, i.e., you are looking at the
|
||||
uses, but not setting them.
|
||||
|
||||
If they do get changed, then care must be taken that things are not changed
|
||||
under the iterators, so use the @code{FOR_EACH_IMM_USE_STMT} and
|
||||
|
|
Loading…
Reference in New Issue