diff options
| author | Nathan Sidwell <nathan@acm.org> | 2020-11-20 10:14:13 -0500 |
|---|---|---|
| committer | Nathan Sidwell <nathan@acm.org> | 2020-11-20 10:14:13 -0500 |
| commit | bf0a3968f5c3eab3f05793f7420d70df9e66acb0 (patch) | |
| tree | 4bfd585895d7f0649eb41dddc1864b63db79089a | |
| parent | 86706296b7e5be80c84846a9a72c4d50fa26ee79 (diff) | |
| download | gcc-bf0a3968f5c3eab3f05793f7420d70df9e66acb0.zip gcc-bf0a3968f5c3eab3f05793f7420d70df9e66acb0.tar.gz gcc-bf0a3968f5c3eab3f05793f7420d70df9e66acb0.tar.bz2 | |
doc: Fixup a couple of formatting nits
I noticed a couple of places we used @code{program} instead of
@command{program}.
gcc/
* doc/invoke.texi: Replace a couple of @code with @command
| -rw-r--r-- | gcc/doc/invoke.texi | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 07232c6..02abac3 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -97,7 +97,7 @@ The usual way to run GCC is to run the executable called @command{gcc}, or When you compile C++ programs, you should invoke GCC as @command{g++} instead. @xref{Invoking G++,,Compiling C++ Programs}, for information about the differences in behavior between @command{gcc} -and @code{g++} when compiling C++ programs. +and @command{g++} when compiling C++ programs. @cindex grouping options @cindex options, grouping @@ -14352,7 +14352,7 @@ Note that it is quite common that execution counts of some part of programs depends, for example, on length of temporary file names or memory space randomization (that may affect hash-table collision rate). Such non-reproducible part of programs may be annotated by -@code{no_instrument_function} function attribute. @code{gcov-dump} with +@code{no_instrument_function} function attribute. @command{gcov-dump} with @option{-l} can be used to dump gathered data and verify that they are indeed reproducible. |