This adds an item to the list of options for the -fdump-tree option,
because we show an example using 'vect' but don't document it.
OK for trunk?
Is there any logic to the order of those options? Would it makes sense
to order them alphabetically?
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 649e2e8a303..491e8f0c694 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+2017-10-13 Jonathan Wakely <jwak...@redhat.com>
+
+ * doc/invoke.texi (-fdump-tree): Document 'vect' option.
+
2017-10-13 Richard Biener <rguent...@suse.de>
* graphite-isl-ast-to-gimple.c
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 4e7dfb33c31..0ff05445143 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -13323,7 +13323,7 @@ instead of the auto named dump files. If the @samp{-@var{options}}
form is used, @var{options} is a list of @samp{-} separated options
which control the details of the dump. Not all options are applicable
to all dumps; those that are not meaningful are ignored. The
-following options are available
+following options are available:
@table @samp
@item address
@@ -13386,6 +13386,8 @@ passes).
@item note
Enable other detailed optimization information (only available in
certain passes).
+@item vect
+Enable showing vectorization information (only available in certain passes).
@item =@var{filename}
Instead of an auto named dump file, output into the given file
name. The file names @file{stdout} and @file{stderr} are treated
