Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932167AbWJANo6 (ORCPT ); Sun, 1 Oct 2006 09:44:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932183AbWJANo6 (ORCPT ); Sun, 1 Oct 2006 09:44:58 -0400 Received: from srv5.dvmed.net ([207.36.208.214]:7563 "EHLO mail.dvmed.net") by vger.kernel.org with ESMTP id S932167AbWJANo5 (ORCPT ); Sun, 1 Oct 2006 09:44:57 -0400 Message-ID: <451FC657.6090603@garzik.org> Date: Sun, 01 Oct 2006 09:44:55 -0400 From: Jeff Garzik User-Agent: Thunderbird 1.5.0.7 (X11/20060913) MIME-Version: 1.0 To: Linux Kernel CC: Andrew Morton Subject: Announce: gcc bogus warning repository Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.3 (----) X-Spam-Report: SpamAssassin version 3.1.3 on srv5.dvmed.net summary: Content analysis details: (-4.3 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1149 Lines: 28 The level of warnings in a kernel build has lately increased to the point where it is hiding bugs and otherwise making life difficult. In particular, recent gcc versions throw warnings when it thinks a variable "MAY be used uninitialized", which is not terribly helpful due to the fact that most of these warnings are bogus. For those that may find this valuable, I have started a git repo that silences these bogus warnings, after careful auditing of code paths to ensure that the warning truly is bogus. The results may be found in the "gccbug" branch of git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git This repository will NEVER EVER be pushed upstream. It exists solely for those who want to decrease their build noise, thereby exposing true bugs. The audit has already uncovered several minor bugs, lending credence to my theory that too many warnings hides bugs. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/