gty calls gt_clear*e*_cache not gt_clear_cache. I know not why it is
named so, but at least document it correctly. invoke.texi had a
duplicate opindex.
gcc/
* doc/gty.texi: Fic gt_cleare_cache name.
* doc/invoke.texi: Remove duplicate opindex Wabi-tag.
pushing to trunk
--
Nathan Sidwell
diff --git i/gcc/doc/gty.texi w/gcc/doc/gty.texi
index 9414d3cc48c..f5c310414dc 100644
--- i/gcc/doc/gty.texi
+++ w/gcc/doc/gty.texi
@@ -250,7 +250,7 @@ for more information.
@findex cache
@item cache
-When the @code{cache} option is applied to a global variable gt_clear_cache is
+When the @code{cache} option is applied to a global variable gt_cleare_cache is
called on that variable between the mark and sweep phases of garbage
collection. The gt_clear_cache function is free to mark blocks as used, or to
clear pointers in the variable.
diff --git i/gcc/doc/invoke.texi w/gcc/doc/invoke.texi
index 09bcc5b0f78..e34d03de002 100644
--- i/gcc/doc/invoke.texi
+++ w/gcc/doc/invoke.texi
@@ -3272,7 +3272,6 @@ In addition, these warning options have meanings only for C++ programs:
@table @gcctabopt
@item -Wabi-tag @r{(C++ and Objective-C++ only)}
@opindex Wabi-tag
-@opindex Wabi-tag
Warn when a type with an ABI tag is used in a context that does not
have that ABI tag. See @ref{C++ Attributes} for more information
about ABI tags.
