From: dnovillo <dnovillo@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Fri, 16 Apr 2010 12:37:55 +0000 (+0000)
Subject: Clarify what happens with an unrecognized -Wno- option
X-Git-Url: http://git.sourceforge.jp/view?p=pf3gnuchains%2Fgcc-fork.git;a=commitdiff_plain;h=f39d98887b1dd32a68dd36ade7424ea5fd1c8a89

Clarify what happens with an unrecognized -Wno- option

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@158413 138bc75d-0d04-0410-961f-82ee72b054a4
---

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 107fabeeebe..39bdff9c901 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -2838,8 +2838,8 @@ two forms, whichever is not the default.  For further,
 language-specific options also refer to @ref{C++ Dialect Options} and
 @ref{Objective-C and Objective-C++ Dialect Options}.
 
-When an unrecognized warning label is requested (e.g.,
-@option{-Wunknown-warning}), GCC will emit a diagnostic stating
+When an unrecognized warning label is requested, for example
+@option{-Wunknwon-warning}, GCC will emit a diagnostic stating
 that the option is not recognized.  However, if the @samp{-Wno-} form
 is used, the behavior is slightly different: No diagnostic will be
 produced for @option{-Wno-unknown-warning} unless other diagnostics