From ca95ce80e05143e64bca88ce5a6a38ee68894a95 Mon Sep 17 00:00:00 2001 From: Vladislav Ivanishin Date: Mon, 7 Oct 2019 14:19:30 +0000 Subject: [PATCH] [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 --- gcc/ChangeLog | 6 ++++++ gcc/doc/invoke.texi | 21 ++++++++++----------- 2 files changed, 16 insertions(+), 11 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index db122e24c47..8ecb2a14812 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,9 @@ +2019-10-07 Vladislav Ivanishin + + * 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 * ipa-prop.c (ipa_vr::nonzero_p): Add TYPE_UNSIGNED check. diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 0b56162f903..107793084b2 100644 --- 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 -- 2.30.2