[PATCH] doc: Use @: where needed

Segher Boessenkool segher@kernel.crashing.org
Wed Nov 7 00:56:00 GMT 2018


When an abbreviation ends with a dot followed by whitespace, Texinfo
thinks the dot ends a sentence, and applies spacing rules etc. based
on that.  To prevent this, there is the @: macro.

This patch puts @: after every vs., e.g., and i.e. where it is needed.
In a few cases there was "@ " already, or "@\n", but @: is slightly
better, and more consistent.

I only spot checked the output.

Is this okay for trunk?


Segher


2018-11-06  Segher Boessenkool  <segher@kernel.crashing.org>

	* target.def: Put @: after every vs., e.g., and i.e. if it is followed
	by whitespace.
	* doc/extend.texi: Ditto.
	* doc/fragments.texi: Ditto.
	* doc/gimple.texi: Ditto.
	* doc/implement-c.texi: Ditto.
	* doc/install.texi: Ditto.
	* doc/invoke.texi: Ditto.
	* doc/md.texi: Ditto.
	* doc/plugins.texi: Ditto.
	* doc/rtl.texi: Ditto.
	* doc/sourcebuild.texi: Ditto.
	* doc/tm.texi.in: Ditto.
	* doc/ux.texi: Ditto.
	* doc/tm.texi: Regenerate.

---
 gcc/doc/extend.texi      | 12 ++++++------
 gcc/doc/fragments.texi   |  2 +-
 gcc/doc/gimple.texi      |  4 ++--
 gcc/doc/implement-c.texi |  2 +-
 gcc/doc/install.texi     | 10 +++++-----
 gcc/doc/invoke.texi      | 50 ++++++++++++++++++++++++------------------------
 gcc/doc/md.texi          | 23 +++++++++++-----------
 gcc/doc/plugins.texi     |  4 ++--
 gcc/doc/rtl.texi         |  4 ++--
 gcc/doc/sourcebuild.texi | 10 +++++-----
 gcc/doc/tm.texi          | 12 ++++++------
 gcc/doc/tm.texi.in       |  6 +++---
 gcc/doc/ux.texi          |  4 ++--
 gcc/target.def           |  6 +++---
 14 files changed, 75 insertions(+), 74 deletions(-)

diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 8d6a8d8..a1f79dc 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -3232,7 +3232,7 @@ change the number of NOPs to any desired value.  The two-value syntax
 is the same as for the command-line switch
 @option{-fpatchable-function-entry=N,M}, generating @var{N} NOPs, with
 the function entry point before the @var{M}th NOP instruction.
-@var{M} defaults to 0 if omitted e.g. function entry point is before
+@var{M} defaults to 0 if omitted e.g.@: function entry point is before
 the first NOP.
 
 If patchable function entries are enabled globally using the command-line
@@ -5322,7 +5322,7 @@ depended upon to work reliably and are not supported.
 @cindex @code{vector} function attribute, RX
 This RX attribute is similar to the @code{interrupt} attribute, including its
 parameters, but does not make the function an interrupt-handler type
-function (i.e. it retains the normal C function calling ABI).  See the
+function (i.e.@: it retains the normal C function calling ABI).  See the
 @code{interrupt} attribute for a description of its arguments.
 @end table
 
@@ -7253,7 +7253,7 @@ possible for these fields to have a different scalar storage order than the
 enclosing type.
 
 This attribute is supported only for targets that use a uniform default
-scalar storage order (fortunately, most of them), i.e. targets that store
+scalar storage order (fortunately, most of them), i.e.@: targets that store
 the scalars either all in big-endian or all in little-endian.
 
 Additional restrictions are enforced for types with the reverse scalar
@@ -8485,7 +8485,7 @@ This code copies @code{src} to @code{dst} and add 1 to @code{dst}.
 GCC's optimizers sometimes discard @code{asm} statements if they determine 
 there is no need for the output variables. Also, the optimizers may move 
 code out of loops if they believe that the code will always return the same 
-result (i.e. none of its input values change between calls). Using the 
+result (i.e.@: none of its input values change between calls). Using the 
 @code{volatile} qualifier disables these optimizations. @code{asm} statements 
 that have no output operands, including @code{asm goto} statements, 
 are implicitly volatile.
@@ -8750,7 +8750,7 @@ Operands are separated by commas.  Each operand has this format:
 Specifies a symbolic name for the operand.
 Reference the name in the assembler template 
 by enclosing it in square brackets 
-(i.e. @samp{%[Value]}). The scope of the name is the @code{asm} statement 
+(i.e.@: @samp{%[Value]}). The scope of the name is the @code{asm} statement 
 that contains the definition. Any valid C variable name is acceptable, 
 including names already defined in the surrounding code. No two operands 
 within the same @code{asm} statement can use the same symbolic name.
@@ -8990,7 +8990,7 @@ Operands are separated by commas.  Each operand has this format:
 Specifies a symbolic name for the operand.
 Reference the name in the assembler template 
 by enclosing it in square brackets 
-(i.e. @samp{%[Value]}). The scope of the name is the @code{asm} statement 
+(i.e.@: @samp{%[Value]}). The scope of the name is the @code{asm} statement 
 that contains the definition. Any valid C variable name is acceptable, 
 including names already defined in the surrounding code. No two operands 
 within the same @code{asm} statement can use the same symbolic name.
diff --git a/gcc/doc/fragments.texi b/gcc/doc/fragments.texi
index b1deb39..314942e 100644
--- a/gcc/doc/fragments.texi
+++ b/gcc/doc/fragments.texi
@@ -212,7 +212,7 @@ the second it will not.
 For configurations that support both multilib and multiarch,
 @code{MULTILIB_OSDIRNAMES} also encodes the multiarch name, thus
 subsuming @code{MULTIARCH_DIRNAME}.  The multiarch name is appended to
-each directory name, separated by a colon (e.g.
+each directory name, separated by a colon (e.g.@:
 @samp{../lib32:i386-linux-gnu}).
 
 Each multiarch subdirectory will be searched before the corresponding OS
diff --git a/gcc/doc/gimple.texi b/gcc/doc/gimple.texi
index 1f9449f..2fa3afb 100644
--- a/gcc/doc/gimple.texi
+++ b/gcc/doc/gimple.texi
@@ -793,7 +793,7 @@ the address of a function local variable).
 
 @deftypefn {GIMPLE function} bool is_gimple_ip_invariant (tree t)
 Return true if t is an interprocedural invariant.  This means that t
-is a valid invariant in all functions (e.g. it can be an address of a
+is a valid invariant in all functions (e.g.@: it can be an address of a
 global variable but not of a local one).
 @end deftypefn
 
@@ -1627,7 +1627,7 @@ Build a @code{GIMPLE_DEBUG} statement with
 statement is to tell debug information generation machinery that the
 user statement at the given @code{location} and @code{block} starts at
 the point at which the statement is inserted.  The intent is that side
-effects (e.g. variable bindings) of all prior user statements are
+effects (e.g.@: variable bindings) of all prior user statements are
 observable, and that none of the side effects of subsequent user
 statements are.
 @end deftypefn
diff --git a/gcc/doc/implement-c.texi b/gcc/doc/implement-c.texi
index 90f47d9..5ac9876 100644
--- a/gcc/doc/implement-c.texi
+++ b/gcc/doc/implement-c.texi
@@ -565,7 +565,7 @@ volatile int *src = @var{somevalue};
 @end smallexample
 
 According to the C standard, such an expression is an rvalue whose type
-is the unqualified version of its original type, i.e. @code{int}.  Whether
+is the unqualified version of its original type, i.e.@: @code{int}.  Whether
 GCC interprets this as a read of the volatile object being pointed to or
 only as a request to evaluate the expression for its side effects depends
 on this type.
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 6c7dac9..41c9b8c 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -1907,7 +1907,7 @@ Specify whether @code{long double} uses the IBM extended double format
 or the IEEE 128-bit floating point format on PowerPC Linux systems.
 This configuration switch will only work on little endian PowerPC
 Linux systems and on big endian 64-bit systems where the default cpu
-is at least power7 (i.e. @option{--with-cpu=power7},
+is at least power7 (i.e.@: @option{--with-cpu=power7},
 @option{--with-cpu=power8}, or @option{--with-cpu=power9} is used).
 
 If you use the @option{--with-long-double-64} configuration option,
@@ -2294,7 +2294,7 @@ continues.
 Specify search directories for the garbage collector header files and
 libraries. @var{list} is a comma separated list of key value pairs of the
 form @samp{@var{multilibdir}=@var{path}}, where the default multilib key
-is named as @samp{.} (dot), or is omitted (e.g.
+is named as @samp{.} (dot), or is omitted (e.g.@:
 @samp{--with-target-bdw-gc=/opt/bdw-gc,32=/opt-bdw-gc32}).
 
 The options @option{--with-target-bdw-gc-include} and
@@ -2302,7 +2302,7 @@ The options @option{--with-target-bdw-gc-include} and
 for each multilib variant and they take precedence over
 @option{--with-target-bdw-gc}.  If @option{--with-target-bdw-gc-include}
 is missing values for a multilib, then the value for the default
-multilib is used (e.g. @samp{--with-target-bdw-gc-include=/opt/bdw-gc/include}
+multilib is used (e.g.@: @samp{--with-target-bdw-gc-include=/opt/bdw-gc/include}
 @samp{--with-target-bdw-gc-lib=/opt/bdw-gc/lib64,32=/opt-bdw-gc/lib32}).
 If none of these options are specified, the library is assumed in
 default locations.
@@ -2483,7 +2483,7 @@ Analogous to @code{bootstrap-O1}.
 Enables Link-Time Optimization for host tools during bootstrapping.
 @samp{BUILD_CONFIG=bootstrap-lto} is equivalent to adding
 @option{-flto} to @samp{BOOT_CFLAGS}.  This option assumes that the host
-supports the linker plugin (e.g. GNU ld version 2.21 or later or GNU gold
+supports the linker plugin (e.g.@: GNU ld version 2.21 or later or GNU gold
 version 2.21 or later).
 
 @item @samp{bootstrap-lto-noplugin}
@@ -2544,7 +2544,7 @@ must be used along with @code{bootstrap-debug-lean} and
 This option enables Intel CET for host tools during bootstrapping.
 @samp{BUILD_CONFIG=bootstrap-cet} is equivalent to adding
 @option{-fcf-protection} to @samp{BOOT_CFLAGS}.  This option
-assumes that the host supports Intel CET (e.g. GNU assembler version
+assumes that the host supports Intel CET (e.g.@: GNU assembler version
 2.30 or later).
 
 @item @samp{bootstrap-time}
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index b6cd0f8..6621200 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -2390,7 +2390,7 @@ Version 9, which first appeared in G++ 5.2, corrects the alignment of
 
 Version 10, which first appeared in G++ 6.1, adds mangling of
 attributes that affect type identity, such as ia32 calling convention
-attributes (e.g. @samp{stdcall}).
+attributes (e.g.@: @samp{stdcall}).
 
 Version 11, which first appeared in G++ 7, corrects the mangling of
 sizeof... expressions and operator names.  For multiple entities with
@@ -2629,7 +2629,7 @@ nonconforming code to compile.
 When an error message refers to a specialization of a function
 template, the compiler normally prints the signature of the
 template followed by the template arguments and any typedefs or
-typenames in the signature (e.g. @code{void f(T) [with T = int]}
+typenames in the signature (e.g.@: @code{void f(T) [with T = int]}
 rather than @code{void f(int)}) so that it's clear which template is
 involved.  When an error message refers to a specialization of a class
 template, the compiler omits any template arguments that match
@@ -2814,7 +2814,7 @@ more things if an older ABI version is selected (with
 
 @option{-Wabi} can also be used with an explicit version number to
 warn about compatibility with a particular @option{-fabi-version}
-level, e.g. @option{-Wabi=2} to warn about changes relative to
+level, e.g.@: @option{-Wabi=2} to warn about changes relative to
 @option{-fabi-version=2}.
 
 If an explicit version number is provided and
@@ -5285,7 +5285,7 @@ void store (int *i)
 @item -Wmaybe-uninitialized
 @opindex Wmaybe-uninitialized
 @opindex Wno-maybe-uninitialized
-For an automatic (i.e.@ local) variable, if there exists a path from the
+For an automatic (i.e.@: local) variable, if there exists a path from the
 function entry to a use of the variable that is initialized, but there exist
 some other paths for which the variable is not initialized, the compiler
 emits a warning if it cannot prove the uninitialized paths are not
@@ -6441,7 +6441,7 @@ Warn when a function pointer is cast to an incompatible function pointer.
 In a cast involving function types with a variable argument list only
 the types of initial arguments that are provided are considered.
 Any parameter of pointer-type matches any other pointer-type.  Any benign
-differences in integral types are ignored, like @code{int} vs. @code{long}
+differences in integral types are ignored, like @code{int} vs.@: @code{long}
 on ILP32 targets.  Likewise type qualifiers are ignored.  The function
 type @code{void (*) (void)} is special and matches everything, which can
 be used to suppress this warning.
@@ -6730,7 +6730,7 @@ the element size.  This warning is enabled by @option{-Wall}.
 @opindex Wmemset-transposed-args
 @opindex Wno-memset-transposed-args
 Warn for suspicious calls to the @code{memset} built-in function, if the
-second argument is not zero and the third argument is zero.  This warns e.g.@
+second argument is not zero and the third argument is zero.  This warns e.g.@:
 about @code{memset (buf, sizeof buf, 0)} where most probably
 @code{memset (buf, 0, sizeof buf)} was meant instead.  The diagnostics
 is only emitted if the third argument is literal zero.  If it is some
@@ -8065,7 +8065,7 @@ Enabled at levels @option{-O2}, @option{-O3}, @option{-Os}.
 
 @item -foptimize-strlen
 @opindex foptimize-strlen
-Optimize various standard C string functions (e.g. @code{strlen},
+Optimize various standard C string functions (e.g.@: @code{strlen},
 @code{strchr} or @code{strcpy}) and
 their @code{_FORTIFY_SOURCE} counterparts into faster alternatives.
 
@@ -8377,7 +8377,7 @@ This option is enabled by default.
 @item -funconstrained-commons
 @opindex funconstrained-commons
 This option tells the compiler that variables declared in common blocks
-(e.g. Fortran) may later be overridden with longer trailing arrays. This
+(e.g.@: Fortran) may later be overridden with longer trailing arrays. This
 prevents certain optimizations that depend on knowing the array bounds.
 
 @item -fcrossjumping
@@ -8504,7 +8504,7 @@ the object is destroyed.  Normally dead store elimination will take
 advantage of this; if your code relies on the value of the object
 storage persisting beyond the lifetime of the object, you can use this
 flag to disable this optimization.  To preserve stores before the
-constructor starts (e.g. because your operator new clears the object
+constructor starts (e.g.@: because your operator new clears the object
 storage) but still treat the object as dead after the destructor you,
 can use @option{-flifetime-dse=1}.  The default behavior can be
 explicitly selected with @option{-flifetime-dse=2}.
@@ -10829,7 +10829,7 @@ for analysis of the number of iterations of the loop tries to evaluate.
 
 @item hot-bb-count-ws-permille
 A basic block profile count is considered hot if it contributes to 
-the given permillage (i.e. 0...1000) of the entire profiled execution.
+the given permillage (i.e.@: 0...1000) of the entire profiled execution.
 
 @item hot-bb-frequency-fraction
 Select fraction of the entry block frequency of executions of basic block in
@@ -10845,7 +10845,7 @@ loop without bounds appears artificially cold relative to the other one.
 
 @item builtin-expect-probability
 Control the probability of the expression having the specified value. This
-parameter takes a percentage (i.e. 0 ... 100) as input.
+parameter takes a percentage (i.e.@: 0 ... 100) as input.
 
 @item builtin-string-cmp-inline-length
 The maximum length of a constant string for a builtin string cmp call 
@@ -11203,7 +11203,7 @@ enable the compiler to find more complex debug expressions, but compile
 time and memory use may grow.
 
 @item max-debug-marker-count
-Sets a threshold on the number of debug markers (e.g. begin stmt
+Sets a threshold on the number of debug markers (e.g.@: begin stmt
 markers) to avoid complexity explosion at inlining or expanding to RTL.
 If a function has more such gimple stmts than the set limit, such stmts
 will be dropped from the inlined copy of a function, and from its RTL
@@ -12130,7 +12130,7 @@ call/jmp-oriented programming (COP/JOP).
 
 The value @code{branch} tells the compiler to implement checking of
 validity of control-flow transfer at the point of indirect branch
-instructions, i.e. call/jmp instructions.  The value @code{return}
+instructions, i.e.@: call/jmp instructions.  The value @code{return}
 implements checking of validity at the point of returning from a
 function.  The value @code{full} is an alias for specifying both
 @code{branch} and @code{return}. The value @code{none} turns off
@@ -12557,7 +12557,7 @@ binary. In this case @option{-fpic} and @option{-fpie} are both disabled.
 If @var{type} is @samp{dyn} the code generation is configured to produce shared
 library. In this case @option{-fpic} or @option{-fPIC} is preserved, but not
 enabled automatically.  This makes it possible to build shared libraries without
-position independent code on architectures this is possible, i.e. on x86.
+position independent code on architectures this is possible, i.e.@: on x86.
 
 If @var{type} is @samp{pie} the code generation is configured to produce
 @option{-fpie} executable. This result in similar optimizations as @samp{exec}
@@ -16053,7 +16053,7 @@ the case.
 @opindex mlra
 Enable Local Register Allocation.  This is still experimental for ARC,
 so by default the compiler uses standard reload
-(i.e. @option{-mno-lra}).
+(i.e.@: @option{-mno-lra}).
 
 @item -mlra-priority-none
 @opindex mlra-priority-none
@@ -16850,7 +16850,7 @@ compiler to select the floating-point and Advanced SIMD instructions
 based on the settings of @option{-mcpu} and @option{-march}.
 
 If the selected floating-point hardware includes the NEON extension
-(e.g. @option{-mfpu=neon}), note that floating-point
+(e.g.@: @option{-mfpu=neon}), note that floating-point
 operations are not generated by GCC's auto-vectorization pass unless
 @option{-funsafe-math-optimizations} is also specified.  This is
 because NEON hardware does not fully implement the IEEE 754 standard for
@@ -17036,7 +17036,7 @@ this option and always use the original scheme.
 
 @item -mword-relocations
 @opindex mword-relocations
-Only generate absolute relocations on word-sized values (i.e. R_ARM_ABS32).
+Only generate absolute relocations on word-sized values (i.e.@: R_ARM_ABS32).
 This is enabled by default on targets (uClinux, SymbianOS) where the runtime
 loader imposes this restriction, and when @option{-fpic} or @option{-fPIC}
 is specified. This option conflicts with @option{-mslow-flash-data}.
@@ -17289,7 +17289,7 @@ resulting address space is not contained in the incoming address space.
 @item -Wmisspelled-isr
 @opindex Wmisspelled-isr
 @opindex Wno-misspelled-isr
-Warn if the ISR is misspelled, i.e. without __vector prefix.
+Warn if the ISR is misspelled, i.e.@: without __vector prefix.
 Enabled by default.
 @end table
 
@@ -22634,7 +22634,7 @@ when linking.  This option is only useful in conjunction with @option{-mhal}.
 @opindex msys-lib
 @var{systemlib} is the library name of the library that provides
 low-level system calls required by the C library,
-e.g. @code{read} and @code{write}.
+e.g.@: @code{read} and @code{write}.
 This option is typically used to link with a library provided by a HAL BSP.
 
 @end table
@@ -22656,7 +22656,7 @@ Generate code for 32-bit or 64-bit ABI.
 
 @item -misa=@var{ISA-string}
 @opindex march
-Generate code for given the specified PTX ISA (e.g.@ @samp{sm_35}).  ISA
+Generate code for given the specified PTX ISA (e.g.@: @samp{sm_35}).  ISA
 strings must be lower-case.  Valid ISA strings include @samp{sm_30} and
 @samp{sm_35}.  The default ISA is sm_30.
 
@@ -23681,7 +23681,7 @@ these instructions.
 
 @item -march=@var{ISA-string}
 @opindex march
-Generate code for given RISC-V ISA (e.g.@ @samp{rv64im}).  ISA strings must be
+Generate code for given RISC-V ISA (e.g.@: @samp{rv64im}).  ISA strings must be
 lower-case.  Examples include @samp{rv64i}, @samp{rv32g}, @samp{rv32e}, and
 @samp{rv32imaf}.
 
@@ -25322,7 +25322,7 @@ facility introduced with the IBM z13 machine generation.
 This option adds support for @samp{vector} to be used as a keyword to
 define vector type variables and arguments.  @samp{vector} is only
 available when GNU extensions are enabled.  It will not be expanded
-when requesting strict standard compliance e.g. with @option{-std=c99}.
+when requesting strict standard compliance e.g.@: with @option{-std=c99}.
 In addition to the GCC low-level builtins @option{-mzvector} enables
 a set of builtins added for compatibility with AltiVec-style
 implementations like Power and Cell.  In order to make use of these
@@ -25693,7 +25693,7 @@ can be overridden by specifying either @option{-mieee} or @option{-mno-ieee}.
 Inline code to invalidate instruction cache entries after setting up
 nested function trampolines.
 This option has no effect if @option{-musermode} is in effect and the selected
-code generation option (e.g. @option{-m4}) does not allow the use of the @code{icbi}
+code generation option (e.g.@: @option{-m4}) does not allow the use of the @code{icbi}
 instruction.
 If the selected code generation option does not allow the use of the @code{icbi}
 instruction, and @option{-musermode} is not in effect, the inlined code
@@ -26953,7 +26953,7 @@ These @samp{-m} options are defined for the VMS implementations:
 @item -mvms-return-codes
 @opindex mvms-return-codes
 Return VMS condition codes from @code{main}. The default is to return POSIX-style
-condition (e.g.@ error) codes.
+condition (e.g.@: error) codes.
 
 @item -mdebug-main=@var{prefix}
 @opindex mdebug-main=@var{prefix}
@@ -28055,7 +28055,7 @@ are generated only when @option{-funsafe-math-optimizations} is enabled
 together with @option{-ffinite-math-only} and @option{-fno-trapping-math}.
 Note that while the throughput of the sequence is higher than the throughput
 of the non-reciprocal instruction, the precision of the sequence can be
-decreased by up to 2 ulp (i.e. the inverse of 1.0 equals 0.99999994).
+decreased by up to 2 ulp (i.e.@: the inverse of 1.0 equals 0.99999994).
 
 Note that GCC implements @code{1.0f/sqrtf(@var{x})} in terms of @code{RSQRTSS}
 (or @code{RSQRTPS}) already with @option{-ffast-math} (or the above option
diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi
index f85935c..ae40f7e 100644
--- a/gcc/doc/md.texi
+++ b/gcc/doc/md.texi
@@ -2021,7 +2021,7 @@ B register
 M register
 
 @item c
-Registers used for circular buffering, i.e. I, B, or L registers.
+Registers used for circular buffering, i.e.@: I, B, or L registers.
 
 @item C
 The CC register.
@@ -4092,7 +4092,7 @@ Second from top of 80387 floating-point stack (@code{%st(1)}).
 
 @ifset INTERNALS
 @item Yk
-Any mask register that can be used as a predicate, i.e. @code{k1-k7}.
+Any mask register that can be used as a predicate, i.e.@: @code{k1-k7}.
 
 @item k
 Any mask register.
@@ -5231,7 +5231,7 @@ calculations.  The expanded code is not allowed to clobber the
 condition code.  It only needs to be defined if @code{add@var{m}3}
 sets the condition code.  If adds used for address calculations and
 normal adds are not compatible it is required to expand a distinct
-pattern (e.g. using an unspec).  The pattern is used by LRA to emit
+pattern (e.g.@: using an unspec).  The pattern is used by LRA to emit
 address calculations.  @code{add@var{m}3} is used if
 @code{addptr@var{m}3} is not defined.
 
@@ -5379,7 +5379,7 @@ of a wider mode.)
 
 @cindex @code{vec_shl_insert_@var{m}} instruction pattern
 @item @samp{vec_shl_insert_@var{m}}
-Shift the elements in vector input operand 1 left one element (i.e.
+Shift the elements in vector input operand 1 left one element (i.e.@:
 away from element 0) and fill the vacated element 0 with the scalar
 in operand 2.  Store the result in vector output operand 0.  Operands
 0 and 1 have mode @var{m} and operand 2 has the mode appropriate for
@@ -5387,7 +5387,7 @@ one element of @var{m}.
 
 @cindex @code{vec_shr_@var{m}} instruction pattern
 @item @samp{vec_shr_@var{m}}
-Whole vector right shift in bits, i.e. towards element 0.
+Whole vector right shift in bits, i.e.@: towards element 0.
 Operand 1 is a vector to be shifted.
 Operand 2 is an integer shift amount in bits.
 Operand 0 is where the resulting shifted vector is stored.
@@ -6156,8 +6156,9 @@ all cases. This expected alignment is also in bytes, just like operand 4.
 Expected size, when unknown, is set to @code{(const_int -1)}.
 Operand 7 is the minimal size of the block and operand 8 is the
 maximal size of the block (NULL if it can not be represented as CONST_INT).
-Operand 9 is the probable maximal size (i.e. we can not rely on it for correctness,
-but it can be used for choosing proper code sequence for a given size).
+Operand 9 is the probable maximal size (i.e.@: we can not rely on it for
+correctness, but it can be used for choosing proper code sequence for a
+given size).
 
 The use for multiple @code{setmem@var{m}} is as for @code{movmem@var{m}}.
 
@@ -7540,8 +7541,8 @@ more flexible approach with one @code{define_expand} is used in GCC.
 The machine description becomes clearer for architectures that
 have compare-and-branch instructions but no condition code.  It also
 works better when different sets of comparison operators are supported
-by different kinds of conditional branches (e.g. integer vs. floating-point),
-or by conditional branches with respect to conditional stores.
+by different kinds of conditional branches (e.g.@: integer vs.@:
+floating-point), or by conditional branches with respect to conditional stores.
 
 Two separate insns are always used if the machine description represents
 a condition code register using the legacy RTL expression @code{(cc0)},
@@ -8878,7 +8879,7 @@ generation. @xref{Disable Insn Alternatives}.
 
 @item mnemonic
 The @code{mnemonic} attribute can be defined to implement instruction
-specific checks in e.g. the pipeline description.
+specific checks in e.g.@: the pipeline description.
 @xref{Mnemonic Attribute}.
 @end table
 
@@ -10211,7 +10212,7 @@ input-template of the @code{define_subst}.  In such case the copy is
 deleted.
 
 @code{define_subst} can be used only in @code{define_insn} and
-@code{define_expand}, it cannot be used in other expressions (e.g. in
+@code{define_expand}, it cannot be used in other expressions (e.g.@: in
 @code{define_insn_and_split}).
 
 @menu
diff --git a/gcc/doc/plugins.texi b/gcc/doc/plugins.texi
index 1eb9a7b..51c88af 100644
--- a/gcc/doc/plugins.texi
+++ b/gcc/doc/plugins.texi
@@ -331,7 +331,7 @@ used to tell if an object is marked, or is about to  be collected.  The
 @code{gt_clear_cache} overloads which some types define may also be of use in
 managing weak references.
 
-Some plugins may need to add extra GGC root tables, e.g. to handle their own
+Some plugins may need to add extra GGC root tables, e.g.@: to handle their own
 @code{GTY}-ed data. This can be done with the @code{PLUGIN_REGISTER_GGC_ROOTS}
 pseudo-event with a null callback and the extra root table (of type @code{struct
 ggc_root_tab*}) as @code{user_data}.  Running the
@@ -471,7 +471,7 @@ When a pass is first added to one of the pass lists, the event
 @section Building GCC plugins
 
 If plugins are enabled, GCC installs the headers needed to build a
-plugin (somewhere in the installation tree, e.g. under
+plugin (somewhere in the installation tree, e.g.@: under
 @file{/usr/local}).  In particular a @file{plugin/include} directory
 is installed, containing all the header files needed to build plugins.
 
diff --git a/gcc/doc/rtl.texi b/gcc/doc/rtl.texi
index a6a63f8..ac8062d 100644
--- a/gcc/doc/rtl.texi
+++ b/gcc/doc/rtl.texi
@@ -1806,7 +1806,7 @@ CONST_VECTOR_NELTS_PER_PATTERN (@var{v}) == 3
 Thus the first 6 elements (@samp{@{ 0, 1, 2, 6, 3, 8 @}}) are enough
 to determine the whole sequence; we refer to them as the ``encoded''
 elements.  They are the only elements present in the square brackets
-for variable-length @code{const_vector}s (i.e. for
+for variable-length @code{const_vector}s (i.e.@: for
 @code{const_vector}s whose mode @var{m} has a variable number of
 elements).  However, as a convenience to code that needs to handle
 both @code{const_vector}s and @code{parallel}s, all elements are
@@ -3417,7 +3417,7 @@ side-effects.
 @item (sequence [@var{insns} @dots{}])
 Represents a sequence of insns.  If a @code{sequence} appears in the
 chain of insns, then each of the @var{insns} that appears in the sequence
-must be suitable for appearing in the chain of insns, i.e. must satisfy
+must be suitable for appearing in the chain of insns, i.e.@: must satisfy
 the @code{INSN_P} predicate.
 
 After delay-slot scheduling is completed, an insn and all the insns that
diff --git a/gcc/doc/sourcebuild.texi b/gcc/doc/sourcebuild.texi
index 7487977..e6630a9 100644
--- a/gcc/doc/sourcebuild.texi
+++ b/gcc/doc/sourcebuild.texi
@@ -66,7 +66,7 @@ include it in @code{libc}.
 The Ada runtime library.
 
 @item libatomic
-The runtime support library for atomic operations (e.g. for @code{__sync}
+The runtime support library for atomic operations (e.g.@: for @code{__sync}
 and @code{__atomic}).
 
 @item libcpp
@@ -2108,7 +2108,7 @@ Target uses a dummy @code{wcsftime} function that always returns zero.
 
 @item fd_truncate
 Target can truncate a file from a file descriptor, as used by
-@file{libgfortran/io/unix.c:fd_truncate}; i.e. @code{ftruncate} or
+@file{libgfortran/io/unix.c:fd_truncate}; i.e.@: @code{ftruncate} or
 @code{chsize}.
 
 @item freestanding
@@ -2156,8 +2156,8 @@ time) should be run on this target.  This can be enabled by setting the
 @env{GCC_TEST_RUN_EXPENSIVE} environment variable to a non-empty string.
 
 @item simulator
-Test system runs executables on a simulator (i.e. slowly) rather than
-hardware (i.e. fast).
+Test system runs executables on a simulator (i.e.@: slowly) rather than
+hardware (i.e.@: fast).
 
 @item signal
 Target has @code{signal.h}.
@@ -3218,7 +3218,7 @@ bb_5:
 
 The @code{startwith} argument indicates at which pass to begin.
 
-Use the dump modifier @code{-gimple} (e.g. @option{-fdump-tree-all-gimple})
+Use the dump modifier @code{-gimple} (e.g.@: @option{-fdump-tree-all-gimple})
 to make tree dumps more closely follow the format accepted by the GIMPLE
 parser.
 
diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi
index f841527..54ca518 100644
--- a/gcc/doc/tm.texi
+++ b/gcc/doc/tm.texi
@@ -1086,7 +1086,7 @@ the default value is @code{BIGGEST_ALIGNMENT}.
 
 On systems that use ELF, the default (in @file{config/elfos.h}) is
 the largest supported 32-bit ELF section alignment representable on
-a 32-bit host e.g. @samp{(((uint64_t) 1 << 28) * 8)}.
+a 32-bit host e.g.@: @samp{(((uint64_t) 1 << 28) * 8)}.
 On 32-bit ELF the largest supported section alignment in bits is
 @samp{(0x80000000 * 8)}, but this is not representable on 32-bit hosts.
 @end defmac
@@ -5086,7 +5086,7 @@ The hook is used for options that have a non-trivial list of possible option val
 Set to true if each call that binds to a local definition explicitly
 clobbers or sets all non-fixed registers modified by performing the call.
 That is, by the call pattern itself, or by code that might be inserted by the
-linker (e.g. stubs, veneers, branch islands), but not including those
+linker (e.g.@: stubs, veneers, branch islands), but not including those
 modifiable by the callee.  The affected registers may be mentioned explicitly
 in the call pattern, or included as clobbers in CALL_INSN_FUNCTION_USAGE.
 The default version of this hook is set to false.  The purpose of this hook
@@ -6319,7 +6319,7 @@ bit) are not set in the same way as a test instruction, so that a different
 branch instruction must be used for some conditional branches.  When
 this happens, use the machine mode of the condition code register to
 record different formats of the condition code register.  Modes can
-also be used to record which compare instruction (e.g. a signed or an
+also be used to record which compare instruction (e.g.@: a signed or an
 unsigned comparison) produced the condition codes.
 
 If other modes than @code{CCmode} are required, add them to
@@ -6586,7 +6586,7 @@ other fields in the same word of the structure, but to different bytes.
 This hook returns true if memory accesses described by the
 @var{mode} and @var{alignment} parameters have a cost many times greater
 than aligned accesses, for example if they are emulated in a trap handler.
-This hook is invoked only for unaligned accesses, i.e. when
+This hook is invoked only for unaligned accesses, i.e.@: when
 @code{@var{alignment} < GET_MODE_ALIGNMENT (@var{mode})}.
 
 When this hook returns true, the compiler will act as if
@@ -10075,7 +10075,7 @@ A C statement to issue assembly directives that create a difference
 
 @defmac ASM_OUTPUT_DWARF_VMS_DELTA (@var{stream}, @var{size}, @var{label1}, @var{label2})
 A C statement to issue assembly directives that create a difference
-between the two given labels in system defined units, e.g. instruction
+between the two given labels in system defined units, e.g.@: instruction
 slots on IA64 VMS, using an integer of the given size.
 @end defmac
 
@@ -11939,7 +11939,7 @@ memory model bits are allowed.
 @end deftypefn
 
 @deftypevr {Target Hook} {unsigned char} TARGET_ATOMIC_TEST_AND_SET_TRUEVAL
-This value should be set if the result written by @code{atomic_test_and_set} is not exactly 1, i.e. the @code{bool} @code{true}.
+This value should be set if the result written by @code{atomic_test_and_set} is not exactly 1, i.e.@: the @code{bool} @code{true}.
 @end deftypevr
 
 @deftypefn {Target Hook} bool TARGET_HAS_IFUNC_P (void)
diff --git a/gcc/doc/tm.texi.in b/gcc/doc/tm.texi.in
index 967ef3a..e8af1bf 100644
--- a/gcc/doc/tm.texi.in
+++ b/gcc/doc/tm.texi.in
@@ -1032,7 +1032,7 @@ the default value is @code{BIGGEST_ALIGNMENT}.
 
 On systems that use ELF, the default (in @file{config/elfos.h}) is
 the largest supported 32-bit ELF section alignment representable on
-a 32-bit host e.g. @samp{(((uint64_t) 1 << 28) * 8)}.
+a 32-bit host e.g.@: @samp{(((uint64_t) 1 << 28) * 8)}.
 On 32-bit ELF the largest supported section alignment in bits is
 @samp{(0x80000000 * 8)}, but this is not representable on 32-bit hosts.
 @end defmac
@@ -4370,7 +4370,7 @@ bit) are not set in the same way as a test instruction, so that a different
 branch instruction must be used for some conditional branches.  When
 this happens, use the machine mode of the condition code register to
 record different formats of the condition code register.  Modes can
-also be used to record which compare instruction (e.g. a signed or an
+also be used to record which compare instruction (e.g.@: a signed or an
 unsigned comparison) produced the condition codes.
 
 If other modes than @code{CCmode} are required, add them to
@@ -6989,7 +6989,7 @@ A C statement to issue assembly directives that create a difference
 
 @defmac ASM_OUTPUT_DWARF_VMS_DELTA (@var{stream}, @var{size}, @var{label1}, @var{label2})
 A C statement to issue assembly directives that create a difference
-between the two given labels in system defined units, e.g. instruction
+between the two given labels in system defined units, e.g.@: instruction
 slots on IA64 VMS, using an integer of the given size.
 @end defmac
 
diff --git a/gcc/doc/ux.texi b/gcc/doc/ux.texi
index adea718..3b395f2 100644
--- a/gcc/doc/ux.texi
+++ b/gcc/doc/ux.texi
@@ -143,7 +143,7 @@ user's source code.  Examples include:
   at the declaration
 
   @item
-  something is erroneously duplicated (e.g. an error, due to breaking a
+  something is erroneously duplicated (e.g.@: an error, due to breaking a
   uniqueness requirement, or a warning, if it's suggestive of a bug)
 
   @item
@@ -545,7 +545,7 @@ hints, rather than replacement fix-it hints.  For example, consider this:
 @end smallexample
 
 @noindent
-which is intended to e.g. replace a @code{std::move} with the underlying
+which is intended to e.g.@: replace a @code{std::move} with the underlying
 value:
 
 @smallexample
diff --git a/gcc/target.def b/gcc/target.def
index ad27d35..4b166d1 100644
--- a/gcc/target.def
+++ b/gcc/target.def
@@ -3552,7 +3552,7 @@ DEFHOOK
  "This hook returns true if memory accesses described by the\n\
 @var{mode} and @var{alignment} parameters have a cost many times greater\n\
 than aligned accesses, for example if they are emulated in a trap handler.\n\
-This hook is invoked only for unaligned accesses, i.e. when\n\
+This hook is invoked only for unaligned accesses, i.e.@: when\n\
 @code{@var{alignment} < GET_MODE_ALIGNMENT (@var{mode})}.\n\
 \n\
 When this hook returns true, the compiler will act as if\n\
@@ -6303,7 +6303,7 @@ DEFHOOKPOD
  "Set to true if each call that binds to a local definition explicitly\n\
 clobbers or sets all non-fixed registers modified by performing the call.\n\
 That is, by the call pattern itself, or by code that might be inserted by the\n\
-linker (e.g. stubs, veneers, branch islands), but not including those\n\
+linker (e.g.@: stubs, veneers, branch islands), but not including those\n\
 modifiable by the callee.  The affected registers may be mentioned explicitly\n\
 in the call pattern, or included as clobbers in CALL_INSN_FUNCTION_USAGE.\n\
 The default version of this hook is set to false.  The purpose of this hook\n\
@@ -6465,7 +6465,7 @@ defined to 1.",
 DEFHOOKPOD
 (atomic_test_and_set_trueval,
  "This value should be set if the result written by\
- @code{atomic_test_and_set} is not exactly 1, i.e. the\
+ @code{atomic_test_and_set} is not exactly 1, i.e.@: the\
  @code{bool} @code{true}.",
  unsigned char, 1)
 
-- 
1.8.3.1



More information about the Gcc-patches mailing list