OpenE2K/gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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

Browse Source 
* 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
This commit is contained in:
Vladislav Ivanishin 2019-10-07 14:19:30 +00:00 committed by Vladislav Ivanishin
parent 19849d1585
commit ca95ce80e0
2 changed files with 16 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gcc/ChangeLog
View File

@ -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.

21
gcc/doc/invoke.texi
View File

@ -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