From owner-freebsd-bugs@FreeBSD.ORG Tue Apr 8 20:10:21 2003 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1441037B401 for ; Tue, 8 Apr 2003 20:10:21 -0700 (PDT) Received: from HAL9000.homeunix.com (12-233-57-131.client.attbi.com [12.233.57.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A92643F3F for ; Tue, 8 Apr 2003 20:10:20 -0700 (PDT) (envelope-from das@freebsd.org) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) h393A9Kj061106; Tue, 8 Apr 2003 20:10:09 -0700 (PDT) (envelope-from das@freebsd.org) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6p2/8.12.5/Submit) id h393A8fa061105; Tue, 8 Apr 2003 20:10:08 -0700 (PDT) (envelope-from das@freebsd.org) Date: Tue, 8 Apr 2003 20:10:08 -0700 From: David Schultz To: Gregory Bond Message-ID: <20030409031008.GA60938@HAL9000.homeunix.com> Mail-Followup-To: Gregory Bond , freebsd-bugs@freebsd.org References: <200304090205.MAA09040@lightning.itga.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200304090205.MAA09040@lightning.itga.com.au> cc: freebsd-bugs@freebsd.org Subject: Re: Two problems with 4.8 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Apr 2003 03:10:21 -0000 On Wed, Apr 09, 2003, Gregory Bond wrote: > [Re: compiler warning msgs from kernel builds] > > > Most of them don't represent real problems, but it wouldn't be a > > bad idea to clean some of them up. > > I've submitted several PRs with patches to remove kernel compile > warnings from -STABLE releases (going back to 2.2.6 IIRC). To my > knowledge, no-one has ever bothered to look at them; certainly they > were never committed. I just gave up about the time 4.1 became -STABLE. > > It might not be a bad idea, but it seems no committer cares enough! Unfortunately, the task of fixing warnings tends to fall to the bottom of most people's priority queues. That's partly because there are enough real bugs out there to keep people busy, and partly because gcc is a rather bad bug-finding tool as bug-finding tools go.