From: Ralf Wildenhues Date: Sat, 13 Sep 2008 18:54:58 +0000 (+0000) Subject: cfg.texi: Fix some typos. X-Git-Tag: releases/gcc-4.4.0~2450 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=d1facce0e3947c1761f18f384adeb51de4411847;p=thirdparty%2Fgcc.git cfg.texi: Fix some typos. gcc/ * doc/cfg.texi: Fix some typos. * doc/extend.texi: Likewise. * doc/install.texi: Likewise. * doc/invoke.texi: Likewise. * doc/rtl.texi: Likewise. * doc/tree-ssa.texi: Likewise. From-SVN: r140347 --- diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 3e9707c2fd94..1e4ce3ebfd05 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,12 @@ +2008-09-13 Ralf Wildenhues + + * doc/cfg.texi: Fix some typos. + * doc/extend.texi: Likewise. + * doc/install.texi: Likewise. + * doc/invoke.texi: Likewise. + * doc/rtl.texi: Likewise. + * doc/tree-ssa.texi: Likewise. + 2008-09-13 Richard Guenther PR middle-end/30141 diff --git a/gcc/doc/cfg.texi b/gcc/doc/cfg.texi index 80440af9c062..323f6b516199 100644 --- a/gcc/doc/cfg.texi +++ b/gcc/doc/cfg.texi @@ -513,9 +513,9 @@ containing the queried statement. When changes need to be applied to a function in its @code{tree} representation, @dfn{block statement iterators} should be used. These iterators provide an integrated abstraction of the flow graph and the -instruction stream. Block statement iterators iterators are -constructed using the @code{block_stmt_iterator} data structure and -several modifier are available, including the following: +instruction stream. Block statement iterators are constructed using +the @code{block_stmt_iterator} data structure and several modifier are +available, including the following: @ftable @code @item bsi_start diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index 32ca1f0b3b02..da9c1daacdcb 100644 --- a/gcc/doc/extend.texi +++ b/gcc/doc/extend.texi @@ -3166,7 +3166,7 @@ declaration without explicit visibility is limited to the visibility of its type. In C++, you can mark member functions and static member variables of a -class with the visibility attribute. This is useful if if you know a +class with the visibility attribute. This is useful if you know a particular method or static member variable should only be used from one shared object; then you can mark it hidden while the rest of the class has default visibility. Care must be taken to avoid breaking @@ -5747,7 +5747,7 @@ backward. Further, instructions will be issued as necessary to prevent the processor from speculating loads across the operation and from queuing stores after the operation. -All of the routines are are described in the Intel documentation to take +All of the routines are described in the Intel documentation to take ``an optional list of variables protected by the memory barrier''. It's not clear what is meant by that; it could mean that @emph{only} the following variables are protected, or it could mean that these variables @@ -12925,13 +12925,13 @@ type. Diagnostic is produced if this requirement is not met. @item __is_class (type) If @code{type} is a cv class type, and not a union type -([basic.compound]) the the trait is true, else it is false. +([basic.compound]) the trait is true, else it is false. @item __is_empty (type) If @code{__is_class (type)} is false then the trait is false. Otherwise @code{type} is considered empty if and only if: @code{type} has no non-static data members, or all non-static data members, if -any, are bit-fields of lenght 0, and @code{type} has no virtual +any, are bit-fields of length 0, and @code{type} has no virtual members, and @code{type} has no virtual base classes, and @code{type} has no base classes @code{base_type} for which @code{__is_empty (base_type)} is false. Requires: @code{type} shall @@ -12939,7 +12939,7 @@ be a complete type, an array type of unknown bound, or is a @code{void} type. @item __is_enum (type) -If @code{type} is a cv enumeration type ([basic.compound]) the the trait is +If @code{type} is a cv enumeration type ([basic.compound]) the trait is true, else it is false. @item __is_pod (type) @@ -12953,7 +12953,7 @@ is true, else it is false. Requires: @code{type} shall be a complete type, an array type of unknown bound, or is a @code{void} type. @item __is_union (type) -If @code{type} is a cv union type ([basic.compound]) the the trait is +If @code{type} is a cv union type ([basic.compound]) the trait is true, else it is false. @end table diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index b51a2405aaa5..8f054229ebdc 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -3134,8 +3134,8 @@ with the @option{--with-ld=@dots{}} option. This overrides the standard search for ld. The two linkers supported on this target require different commands. The default linker is determined during configuration. As a result, it's not possible to switch linkers in the middle of a GCC build. -This has been been reported to sometimes occur in unified builds of -binutils and GCC@. +This has been reported to sometimes occur in unified builds of binutils +and GCC@. GCC 3.0 through 3.2 require binutils 2.11 or above. GCC 3.3 through GCC 4.0 require binutils 2.14 or later. diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 1f0077fa7d00..eb9ecd555c04 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -1522,7 +1522,7 @@ known not to modify global memory. With the @option{-fno-builtin-@var{function}} option only the built-in function @var{function} is disabled. @var{function} must not begin with @samp{__builtin_}. If a -function is named this is not built-in in this version of GCC, this +function is named that is not built-in in this version of GCC, this option is ignored. There is no corresponding @option{-fbuiltin-@var{function}} option; if you wish to enable built-in functions selectively when using @option{-fno-builtin} or @@ -5081,7 +5081,7 @@ Don't forget the trailing @samp{/}. @opindex print-sysroot Print the target sysroot directory that will be used during compilation. This is the target sysroot specified either at configure -time or or using the @option{--sysroot} option, possibly with an extra +time or using the @option{--sysroot} option, possibly with an extra suffix that depends on compilation options. If no target sysroot is specified, the option prints nothing. @@ -7084,7 +7084,7 @@ The default value is 90. @item large-function-insns The limit specifying really large functions. For functions larger than this -limit after inlining inlining is constrained by +limit after inlining, inlining is constrained by @option{--param large-function-growth}. This parameter is useful primarily to avoid extreme compilation time caused by non-linear algorithms used by the backend. @@ -10931,7 +10931,7 @@ the system libraries and startup modules. Set 80387 floating-point precision to 32, 64 or 80 bits. When @option{-mpc32} is specified, the significands of results of floating-point operations are -rounded to 24 bits (single precision); @option{-mpc64} rounds the the +rounded to 24 bits (single precision); @option{-mpc64} rounds the significands of results of floating-point operations to 53 bits (double precision) and @option{-mpc80} rounds the significands of results of floating-point operations to 64 bits (extended double precision), which is diff --git a/gcc/doc/rtl.texi b/gcc/doc/rtl.texi index e28d52382275..148e19ddc9a1 100644 --- a/gcc/doc/rtl.texi +++ b/gcc/doc/rtl.texi @@ -3703,7 +3703,7 @@ insn-field) goes into the @code{JUMP_LABEL} field and does not have a This insn is an branching instruction (either an unconditional jump or an indirect jump) which crosses between hot and cold sections, which could potentially be very far apart in the executable. The presence -of this note indicates to other optimizations that this this branching +of this note indicates to other optimizations that this branching instruction should not be ``collapsed'' into a simpler branching construct. It is used when the optimization to partition basic blocks into hot and cold sections is turned on. diff --git a/gcc/doc/tree-ssa.texi b/gcc/doc/tree-ssa.texi index 0bf89b22be48..ea3d0ab4c595 100644 --- a/gcc/doc/tree-ssa.texi +++ b/gcc/doc/tree-ssa.texi @@ -1045,7 +1045,7 @@ FOR_EACH_PHI_ARG (use_p, phi_stmt, iter, SSA_OP_VIRTUAL_USES) FOR_EACH_PHI_ARG (use_p, phi_stmt, iter, SSA_OP_USES) my_code; -/* Look at every every PHI use. */ +/* Look at every PHI use. */ FOR_EACH_PHI_ARG (use_p, phi_stmt, iter, SSA_OP_ALL_USES) my_code; @end smallexample @@ -1131,7 +1131,7 @@ Some useful functions and macros: single use of @code{ssa_var}. @item @code{single_imm_use (ssa_var, use_operand_p *ptr, tree *stmt)} : Returns true if there is only a single use of @code{ssa_var}, and also returns -the use pointer and statement it occurs in in the second and third parameters. +the use pointer and statement it occurs in, in the second and third parameters. @item @code{num_imm_uses (ssa_var)} : Returns the number of immediate uses of @code{ssa_var}. It is better not to use this if possible since it simply utilizes a loop to count the uses.