From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:51318) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TSED2-00068C-RN for qemu-devel@nongnu.org; Sat, 27 Oct 2012 17:46:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TSED1-00015O-Gk for qemu-devel@nongnu.org; Sat, 27 Oct 2012 17:46:24 -0400 Received: from v220110690675601.yourvserver.net ([78.47.199.172]:57853) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TSED1-00015E-Ab for qemu-devel@nongnu.org; Sat, 27 Oct 2012 17:46:23 -0400 Message-ID: <508C562C.8060708@weilnetz.de> Date: Sat, 27 Oct 2012 23:46:20 +0200 From: Stefan Weil MIME-Version: 1.0 References: <1350244839-16875-1-git-send-email-peter.maydell@linaro.org> <508C44C0.8070301@gmail.com> <508C50FE.5070003@weilnetz.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] configure: Disable (clang) initializer-overrides warnings List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Igor Mitsyanko , Blue Swirl , qemu-devel@nongnu.org, patches@linaro.org Am 27.10.2012 23:35, schrieb Peter Maydell: > On 27 October 2012 22:24, Stefan Weil wrote: >> Am 27.10.2012 22:32, schrieb Igor Mitsyanko: >>> I encountered strange behavior of latest mingw gcc, it ignores >>> unrecognized -Wno-wombat options only in case if no other warnings are >>> issued (configure gccflags test doesn't issue any), otherwise I get this: >>> >>> cc1.exe: warning: unrecognized command line option >>> "-Wno-initializer-overrides" [enabled by default] >>> >>> This is probably a bug in mingw GCC (or perhaps I'm using it wrong), but >>> anyway, this makes QEMU mingw build output very noisy. >> This "feature" of gcc is not restricted to MinGW nor to a special version of >> gcc but can also occur on Linux. > > Incidentally, I was tangentially involved in getting gcc to adopt > this behaviour. The rationale is that it allows you to write > straightforward makefiles which use -Werror and also some -Wno-* > options without having to add some configure-like step to test > whether gcc supports the -Wno-*. If the gcc version you're using > doesn't support detecting the presence of wombats in your source > code then it will never produce warnings about them, so it's > safe for it to treat -Wno-wombat as a no-op. The reason for > printing the message if some other warning is also emitted is > so the user can spot the case where they accidentally typo'd > the -Wno-* option they meant to use to suppress the warning. > > -- PMM Nice. Thanks for that explanation. Are there plans to add wombat detection to gcc? :-) Here is the spec: http://upload.wikimedia.org/wikipedia/commons/1/18/Vombatus_ursinus_-Maria_Island_National_Park.jpg Stefan