* doc/invoke.texi (-Wuninitialized): Clarify -O connection.

From-SVN: r113048

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 6b3d3f67d7b4e6cc58273b63651d4fada5296080..4e1a2e152879f79d44c8a61789a1c08fbd424e8e 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+2006-04-18  Devang Patel  <dpatel@apple.com>
+
+       * doc/invoke.texi (-Wuninitialized): Clarify -O connection.
+       
 2006-04-18  Nick Clifton  <nickc@redhat.com>
 
        * config/sh/t-symbian: Add rule to build sh-c.o

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 7080aacf8bbdcfe1025778955c44344cefe45ae1..5dcf70b974728514fd6ae2ead19d992f1a3c5d28 100644 (file)
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -2682,8 +2682,9 @@ if a variable may be clobbered by a @code{setjmp} call.
 
 These warnings are possible only in optimizing compilation,
 because they require data flow information that is computed only
-when optimizing.  If you don't specify @option{-O}, you simply won't
-get these warnings.
+when optimizing.  If you do not specify @option{-O}, you will not get 
+these warnings. Instead, GCC will issue a warning about @option{-Wuninitialized}
+requiring @option{-O}.
 
 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.