mirror/gcc
2
0
Fork 0
mirror of git://gcc.gnu.org/git/gcc.git synced 2025-03-01 12:06:16 +08:00
Code Issues Packages Projects Releases Wiki Activity

doc: Fixup a couple of formatting nits

Browse Source 
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
This commit is contained in:
Nathan Sidwell 2020-11-20 10:14:13 -05:00
parent 86706296b7
commit bf0a3968f5
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gcc/doc/invoke.texi
View File

@ -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.