The description of the default behavour of -fopt-info in invoke.texi is
wrong. This patch fixes it. I also added a sentence to explicitly say
what is implied by the note that -fopt-info-vec-missed is the same as
-fopt-info-missed-vec. Namely, that order doesn't matter.
OK to checkin?
Steve Ellcey
sell...@cavium.com
2017-05-03 Steve Ellcey <sell...@cavium.com>
* doc/invoke.texi (-fopt-info): Fix description of default
behavour. Explicitly say order of options included in -fopt-info
does not matter.
diff --git a/gcc/doc/optinfo.texi b/gcc/doc/optinfo.texi
index e17cb37..f4158a0 100644
--- a/gcc/doc/optinfo.texi
+++ b/gcc/doc/optinfo.texi
@@ -208,16 +208,17 @@ optimized locations from all the inlining passes into
If the @var{filename} is provided, then the dumps from all the
applicable optimizations are concatenated into the @file{filename}.
Otherwise the dump is output onto @file{stderr}. If @var{options} is
-omitted, it defaults to @option{all-all}, which means dump all
-available optimization info from all the passes. In the following
-example, all optimization info is output on to @file{stderr}.
+omitted, it defaults to @option{optimized-optall}, which means dump
+information about successfully applied optimizations from all the passes.
+In the following example, the optimization info is output on to @file{stderr}.
@smallexample
gcc -O3 -fopt-info
@end smallexample
Note that @option{-fopt-info-vec-missed} behaves the same as
-@option{-fopt-info-missed-vec}.
+@option{-fopt-info-missed-vec}. The order of the optimization group
+names and message types listed after @option{-fopt-info} does not matter.
As another example, consider
