From: jsm28 Date: Mon, 9 May 2005 23:51:49 +0000 (+0000) Subject: PR c/21160 X-Git-Tag: upstream/4.9.2~61342 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=98e8aa2ea9bd331873681023998ffbc41954c17b;p=platform%2Fupstream%2Flinaro-gcc.git PR c/21160 * doc/invoke.texi (-Wuninitialized): Update documentation. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@99478 138bc75d-0d04-0410-961f-82ee72b054a4 --- diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 4f0f859..44126a2 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,8 @@ +2005-05-09 Joseph S. Myers + + PR c/21160 + * doc/invoke.texi (-Wuninitialized): Update documentation. + 2005-05-09 Richard Earnshaw * arm.c (const_ok_for_arm): Use a faster algorithm. diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 52d879c..656a5d4 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -2565,11 +2565,13 @@ get these warnings. If you want to warn about code which uses the uninitialized value of the variable in its own initializer, use the @option{-Winit-self} option. -These warnings occur only for variables that are candidates for -register allocation. Therefore, they do not occur for a variable that -is declared @code{volatile}, or whose address is taken, or whose size -is other than 1, 2, 4 or 8 bytes. Also, they do not occur for -structures, unions or arrays, even when they are in registers. +These warnings occur for individual uninitialized or clobbered +elements of structure, union or array variables as well as for +variables which 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 will 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