[doc] -Wuninitialized doesn't do -Wclobbered's job

        * gcc/doc/invoke.texi (-Wuninitialized): Don't mention the clobbered by
        setjmp situation here.  Fix a verb's ending: "the exact variables or
        elements for which there are warnings depends" -> "... depend".

From-SVN: r276657

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index db122e24c475727234e5d75ad2d0e45bbbe05b24..8ecb2a148126c4e067edde4057166340b44e2745 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,9 @@
+2019-10-07 Vladislav Ivanishin  <vlad@ispras.ru>
+
+       * doc/invoke.texi (-Wuninitialized): Don't mention the clobbered by
+       setjmp situation here.  Fix a verb's ending: "the exact variables or
+       elements for which there are warnings depends" -> "... depend".
+
 2019-10-07  Aldy Hernandez  <aldyh@redhat.com>
 
        * ipa-prop.c (ipa_vr::nonzero_p): Add TYPE_UNSIGNED check.

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 0b56162f9032297012cb5ca0f1503f90933d6fba..107793084b28a565ecfbb24cf9a8d5cb73323861 100644 (file)
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -5578,21 +5578,20 @@ either specify @option{-Wextra -Wunused} (note that @option{-Wall} implies
 @item -Wuninitialized
 @opindex Wuninitialized
 @opindex Wno-uninitialized
-Warn if an automatic variable is used without first being initialized
-or if a variable may be clobbered by a @code{setjmp} call. In C++,
-warn if a non-static reference or non-static @code{const} member
-appears in a class without constructors.
+Warn if an automatic variable is used without first being initialized.
+In C++, warn if a non-static reference or non-static @code{const}
+member appears in a class without constructors.
 
 If you want to warn about code that uses the uninitialized value of the
 variable in its own initializer, use the @option{-Winit-self} option.
 
-These warnings occur for individual uninitialized or clobbered
-elements of structure, union or array variables as well as for
-variables that are uninitialized or clobbered as a whole.  They do
-not occur for variables or elements declared @code{volatile}.  Because
-these warnings depend on optimization, the exact variables or elements
-for which there are warnings depends on the precise optimization
-options and version of GCC used.
+These warnings occur for individual uninitialized elements of
+structure, union or array variables as well as for variables that are
+uninitialized as a whole.  They do not occur for variables or elements
+declared @code{volatile}.  Because these warnings depend on
+optimization, the exact variables or elements for which there are
+warnings depend on the precise optimization options and version of GCC
+used.
 
 Note that there may be no warning about a variable that is used only
 to compute a value that itself is never used, because such