Commit 5734f2b3 by Jonathan Wakely Committed by Jonathan Wakely

invoke.texi (Warning Options): Add missing hyphen.

2011-01-25  Jonathan Wakely  <jwakely.gcc@gmail.com>

	* doc/invoke.texi (Warning Options): Add missing hyphen.
	(-fprofile-dir): Minor grammatical fixes.
	(-fbranch-probabilities): Likewise.

From-SVN: r169261
parent 9bdbdcef
2011-01-25 Jonathan Wakely <jwakely.gcc@gmail.com>
* doc/invoke.texi (Warning Options): Add missing hyphen.
(-fprofile-dir): Minor grammatical fixes.
(-fbranch-probabilities): Likewise.
2011-01-25 Alexandre Oliva <aoliva@redhat.com>
PR debug/45136
......
......@@ -229,7 +229,7 @@ Objective-C and Objective-C++ Dialects}.
@item Warning Options
@xref{Warning Options,,Options to Request or Suppress Warnings}.
@gccoptlist{-fsyntax-only fmax-errors=@var{n} -pedantic @gol
@gccoptlist{-fsyntax-only -fmax-errors=@var{n} -pedantic @gol
-pedantic-errors @gol
-w -Wextra -Wall -Waddress -Waggregate-return -Warray-bounds @gol
-Wno-attributes -Wno-builtin-macro-redefined @gol
......@@ -7720,13 +7720,13 @@ default, GCC will emit an error message when an inconsistent profile is detected
@item -fprofile-dir=@var{path}
@opindex fprofile-dir
Set the directory to search the profile data files in to @var{path}.
Set the directory to search for the profile data files in to @var{path}.
This option affects only the profile data generated by
@option{-fprofile-generate}, @option{-ftest-coverage}, @option{-fprofile-arcs}
and used by @option{-fprofile-use} and @option{-fbranch-probabilities}
and its related options.
By default, GCC will use the current directory as @var{path}
thus the profile data file will appear in the same directory as the object file.
By default, GCC will use the current directory as @var{path}, thus the
profile data file will appear in the same directory as the object file.
@item -fprofile-generate
@itemx -fprofile-generate=@var{path}
......@@ -8011,7 +8011,7 @@ With @option{-fbranch-probabilities}, GCC puts a
@samp{REG_BR_PROB} note on each @samp{JUMP_INSN} and @samp{CALL_INSN}.
These can be used to improve optimization. Currently, they are only
used in one place: in @file{reorg.c}, instead of guessing which path a
branch is mostly to take, the @samp{REG_BR_PROB} values are used to
branch is most likely to take, the @samp{REG_BR_PROB} values are used to
exactly determine which path is taken more often.
@item -fprofile-values
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment