From: Devang Patel <dpatel@apple.com>
Date: Tue, 18 Apr 2006 16:06:32 +0000 (-0700)
Subject: * doc/invoke.texi (-Wuninitialized): Clarify -O connection.
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=d955420ef2745f2a2c8ec7f0f6d2e2bd1296afb9;p=gcc.git

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

From-SVN: r113048
---

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 6b3d3f67d7b..4e1a2e15287 100644
--- 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 7080aacf8bb..5dcf70b9747 100644
--- 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.