diff options
author | gerald <gerald@138bc75d-0d04-0410-961f-82ee72b054a4> | 2007-01-28 19:26:29 +0000 |
---|---|---|
committer | gerald <gerald@138bc75d-0d04-0410-961f-82ee72b054a4> | 2007-01-28 19:26:29 +0000 |
commit | 59971b4df5473572ca984df9c9a934bccef4f2a8 (patch) | |
tree | 30c6d1df026553a9c4d0f76323108aea56c457ff /gcc/doc | |
parent | 1d11da7796c4a50189b18151e5dc6dc385c95e24 (diff) | |
download | gcc-59971b4df5473572ca984df9c9a934bccef4f2a8.tar.gz |
* 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.
* doc/install.texi: Likewise.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/branches/gcc-4_1-branch@121267 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/doc')
-rw-r--r-- | gcc/doc/c-tree.texi | 2 | ||||
-rw-r--r-- | gcc/doc/cppinternals.texi | 2 | ||||
-rw-r--r-- | gcc/doc/extend.texi | 4 | ||||
-rw-r--r-- | gcc/doc/install.texi | 2 | ||||
-rw-r--r-- | gcc/doc/passes.texi | 4 | ||||
-rw-r--r-- | gcc/doc/sourcebuild.texi | 2 | ||||
-rw-r--r-- | gcc/doc/tree-ssa.texi | 8 |
7 files changed, 12 insertions, 12 deletions
diff --git a/gcc/doc/c-tree.texi b/gcc/doc/c-tree.texi index a7183fc2400..e17ba4b4148 100644 --- a/gcc/doc/c-tree.texi +++ b/gcc/doc/c-tree.texi @@ -2127,7 +2127,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. diff --git a/gcc/doc/cppinternals.texi b/gcc/doc/cppinternals.texi index 13db034b0ca..241c00a5a1d 100644 --- a/gcc/doc/cppinternals.texi +++ b/gcc/doc/cppinternals.texi @@ -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 diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index ce0a702d0f3..bed6e1e10a3 100644 --- a/gcc/doc/extend.texi +++ b/gcc/doc/extend.texi @@ -1236,7 +1236,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. @@ -10600,7 +10600,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++. diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index 5ea9dbb17d6..9512be4a689 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -864,7 +864,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 diff --git a/gcc/doc/passes.texi b/gcc/doc/passes.texi index 3a062457dc7..82b95f8fb0b 100644 --- a/gcc/doc/passes.texi +++ b/gcc/doc/passes.texi @@ -204,7 +204,7 @@ by @code{pass_mudflap_1}. @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 @@ -313,7 +313,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}. diff --git a/gcc/doc/sourcebuild.texi b/gcc/doc/sourcebuild.texi index ab31381216a..3a274807cd3 100644 --- a/gcc/doc/sourcebuild.texi +++ b/gcc/doc/sourcebuild.texi @@ -833,7 +833,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 diff --git a/gcc/doc/tree-ssa.texi b/gcc/doc/tree-ssa.texi index 77a2f0a01ab..c143570390f 100644 --- a/gcc/doc/tree-ssa.texi +++ b/gcc/doc/tree-ssa.texi @@ -869,7 +869,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 @@ -1098,9 +1098,9 @@ to change each use of @code{ssa_var} to @code{ssa_var2}: SET_USE (imm_use_p, ssa_var_2); @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_SAFE} iterator. It |