Hi Sandra,
On Wed, 29 Aug 2012, Sandra Loosemore wrote:
> I've had this largish pile of random copy-edits to invoke.texi left over
> from my previous passes through that file earlier this year.
that was an amazing amount of changes; I admire your patience and
thoroughness!
> I'll wait a few days before committing to give folks a chance to object
> and/or volunteer to review the whole patch. ;-)
That was more like a few years, but I did go through the patch. :-o
On thing I noticed is that you converted "nop" to "NOP", is that
a standard you generally suggest to establish? If so, I've got a
couple more cases.
Let me know, and I'll apply this patch.
Gerald
2016-09-01 Gerald Pfeifer <ger...@pfeifer.com>
* doc/invoke.texi (SPU Options): nops -> NOPs.
(x86 Options): Ditto.
Index: doc/invoke.texi
===================================================================
--- doc/invoke.texi (revision 239904)
+++ doc/invoke.texi (working copy)
@@ -22807,16 +22807,16 @@
@item -mdual-nops
@itemx -mdual-nops=@var{n}
@opindex mdual-nops
-By default, GCC inserts nops to increase dual issue when it expects
+By default, GCC inserts NOPs to increase dual issue when it expects
it to increase performance. @var{n} can be a value from 0 to 10. A
-smaller @var{n} inserts fewer nops. 10 is the default, 0 is the
+smaller @var{n} inserts fewer NOPs. 10 is the default, 0 is the
same as @option{-mno-dual-nops}. Disabled with @option{-Os}.
@item -mhint-max-nops=@var{n}
@opindex mhint-max-nops
-Maximum number of nops to insert for a branch hint. A branch hint must
+Maximum number of NOPs to insert for a branch hint. A branch hint must
be at least 8 instructions away from the branch it is affecting. GCC
-inserts up to @var{n} nops to enforce this, otherwise it does not
+inserts up to @var{n} NOPs to enforce this, otherwise it does not
generate the branch hint.
@item -mhint-max-distance=@var{n}
@@ -24601,7 +24601,7 @@
@itemx -mno-nop-mcount
@opindex mnop-mcount
If profiling is active (@option{-pg}), generate the calls to
-the profiling functions as nops. This is useful when they
+the profiling functions as NOPs. This is useful when they
should be patched in later dynamically. This is likely only
useful together with @option{-mrecord-mcount}.
