gcc/ChangeLog: 2008-02-14 Ralf Wildenhues * doc/extend.texi: Use @: or add comma where appropriate. * doc/invoke.texi: Likewise. * doc/tm.texi: Likewise. diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index 055dd26..1d53a07 100644 --- a/gcc/doc/extend.texi +++ b/gcc/doc/extend.texi @@ -5649,7 +5649,7 @@ assert (__builtin_object_size (q, 1) == sizeof (var.b)); @end deftypefn There are built-in functions added for many common string operation -functions, e.g. for @code{memcpy} @code{__builtin___memcpy_chk} +functions, e.g., for @code{memcpy} @code{__builtin___memcpy_chk} built-in is provided. This built-in has an additional last argument, which is the number of bytes remaining in object the @var{dest} argument points to or @code{(size_t) -1} if the size is not known. @@ -5702,7 +5702,7 @@ int __builtin___vsnprintf_chk (char *s, size_t maxlen, int flag, size_t os, @end smallexample The added @var{flag} argument is passed unchanged to @code{__sprintf_chk} -etc. functions and can contain implementation specific flags on what +etc.@: functions and can contain implementation specific flags on what additional security measures the checking function might take, such as handling @code{%n} differently. @@ -5718,7 +5718,7 @@ In addition to this, there are checking built-in functions @code{__builtin___fprintf_chk} and @code{__builtin___vfprintf_chk}. These have just one additional argument, @var{flag}, right before format string @var{fmt}. If the compiler is able to optimize them to -@code{fputc} etc. functions, it will, otherwise the checking function +@code{fputc} etc.@: functions, it will, otherwise the checking function should be called and the @var{flag} argument passed to it. @node Other Builtins @@ -11067,7 +11067,7 @@ multiple @code{#pragma pack(@var{n})} instances and finalized by a single @code{#pragma pack(pop)}. @end enumerate -Some targets, e.g. i386 and powerpc, support the @code{ms_struct} +Some targets, e.g.@: i386 and powerpc, support the @code{ms_struct} @code{#pragma} which lays out a structure as the documented @code{__attribute__ ((ms_struct))}. @enumerate diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 8d8d959..2809812 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -1181,7 +1181,7 @@ switches supported by the compiler the following can be used: The sense of a qualifier can be inverted by prefixing it with the @var{^} character, so for example to display all binary warning -options (i.e. ones that are either on or off and that do not take an +options (i.e., ones that are either on or off and that do not take an argument), which have a description the following can be used: @smallexample @@ -4920,16 +4920,16 @@ For @var{n}=0 no diagnostic information is reported. If @var{n}=1 the vectorizer reports each loop that got vectorized, and the total number of loops that got vectorized. If @var{n}=2 the vectorizer also reports non-vectorized loops that passed -the first analysis phase (vect_analyze_loop_form) - i.e. countable, +the first analysis phase (vect_analyze_loop_form) - i.e.@: countable, inner-most, single-bb, single-entry/exit loops. This is the same verbosity level that @option{-fdump-tree-vect-stats} uses. Higher verbosity levels mean either more information dumped for each reported loop, or same amount of information reported for more loops: If @var{n}=3, alignment related information is added to the reports. -If @var{n}=4, data-references related information (e.g. memory dependences, +If @var{n}=4, data-references related information (e.g.@: memory dependences, memory access-patterns) is added to the reports. If @var{n}=5, the vectorizer reports also non-vectorized inner-most loops -that did not pass the first analysis phase (i.e. may not be countable, or +that did not pass the first analysis phase (i.e., may not be countable, or may have complicated control-flow). If @var{n}=6, the vectorizer reports also non-vectorized nested loops. For @var{n}=7, all the information the vectorizer generates during its @@ -5936,7 +5936,7 @@ Parallelize loops, i.e., split their iteration space to run in n threads. This is only possible for loops whose iterations are independent and can be arbitrarily reordered. The optimization is only profitable on multiprocessor machines, for loops that are CPU-intensive, -rather than constrained e.g. by memory bandwidth. This option +rather than constrained e.g.@: by memory bandwidth. This option implies @option{-pthread}, and thus is only supported on targets that have support for @option{-pthread}. diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi index 54d6113..5207953 100644 --- a/gcc/doc/tm.texi +++ b/gcc/doc/tm.texi @@ -5483,7 +5483,7 @@ widening multiplication of the even elements of two input vectors of type @var{x If this hook is defined, the autovectorizer will use it along with the @code{TARGET_VECTORIZE_BUILTIN_MUL_WIDEN_ODD} target hook when vectorizing widening multiplication in cases that the order of the results does not have to be -preserved (e.g. used only by a reduction computation). Otherwise, the +preserved (e.g.@: used only by a reduction computation). Otherwise, the @code{widen_mult_hi/lo} idioms will be used. @end deftypefn @@ -5494,7 +5494,7 @@ widening multiplication of the odd elements of two input vectors of type @var{x} If this hook is defined, the autovectorizer will use it along with the @code{TARGET_VECTORIZE_BUILTIN_MUL_WIDEN_EVEN} target hook when vectorizing widening multiplication in cases that the order of the results does not have to be -preserved (e.g. used only by a reduction computation). Otherwise, the +preserved (e.g.@: used only by a reduction computation). Otherwise, the @code{widen_mult_hi/lo} idioms will be used. @end deftypefn @@ -6214,14 +6214,14 @@ used to initialize data used by the previous hook. @deftypefn {Target Hook} void TARGET_SCHED_DFA_PRE_CYCLE_ADVANCE (void) The hook to notify target that the current simulated cycle is about to finish. The hook is analogous to @samp{TARGET_SCHED_DFA_PRE_CYCLE_INSN} but used -to change the state in more complicated situations - e.g. when advancing +to change the state in more complicated situations - e.g., when advancing state on a single insn is not enough. @end deftypefn @deftypefn {Target Hook} void TARGET_SCHED_DFA_POST_CYCLE_ADVANCE (void) The hook to notify target that new simulated cycle has just started. The hook is analogous to @samp{TARGET_SCHED_DFA_POST_CYCLE_INSN} but used -to change the state in more complicated situations - e.g. when advancing +to change the state in more complicated situations - e.g., when advancing state on a single insn is not enough. @end deftypefn