From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:50206) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Twzh2-0007Hg-CN for qemu-devel@nongnu.org; Sun, 20 Jan 2013 13:32:35 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Twzh0-00029Z-4Y for qemu-devel@nongnu.org; Sun, 20 Jan 2013 13:32:32 -0500 From: Paul Brook Date: Sun, 20 Jan 2013 18:32:14 +0000 References: <19952e84d566d9309b15fe205db6b166f4234c33.1358697255.git.blauwirbel@gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-ID: <201301201832.15780.paul@codesourcery.com> Subject: Re: [Qemu-devel] [PATCH] Annotate questionable fallthroughs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Kevin Wolf , Peter Crosthwaite , Anthony Liguori , Mark Langsdorf , qemu-ppc@nongnu.org, Riku Voipio , qemu-devel@nongnu.org, Alexander Graf , Blue Swirl , Max Filippov , "Vassili Karpov (malc)" , Paolo Bonzini , Guan Xuetao , Aurelien Jarno , Richard Henderson > I don't think there's much point adding tons of "XXX" comments > when a bunch of these aren't actually wrong code. If you want to fix > this I think a better approach would be more focused patches aimed > at adding 'break;' or "/* fallthrough */" based on actual human > examination of the surrounding code. I agree. I encourage annotation of intentional fall through, but blindly pasting the output of an automated tool is liable to cause more harm than good. IMO running code analysis tools is easy. It's only when you take the time to manually inspect and fix the code that this really becomes valuable. Paul