From owner-freebsd-current Sun Nov 10 00:26:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA23680 for current-outgoing; Sun, 10 Nov 1996 00:26:54 -0800 (PST) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA23674 for ; Sun, 10 Nov 1996 00:26:50 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id DAA11968; Sun, 10 Nov 1996 03:26:40 -0500 (EST) From: "John S. Dyson" Message-Id: <199611100826.DAA11968@dyson.iquest.net> Subject: Re: Some fundamental datatype change? Excessive unsigned vs signed compare warnings on kernel builds. To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Sun, 10 Nov 1996 03:26:39 -0500 (EST) Cc: current@FreeBSD.org In-Reply-To: from "Jaye Mathisen" at Nov 9, 96 11:59:06 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > I haven't actually watched a full kernel build in a while, just copying > the result to /. However, I've been messing with Justin's new AHC code, > and just happened to watch a compile of a -current downloaded around 11/7, > and there's lots of warnings about compares of unsigned vs. signed. > > Normally these don't worry me, but there were numerous ones in the FS > stuff, a few in the vm section, and oodles in the NFS stuff. Just seems > unhealthy. > Yep, I kind-of agree with you. I certainly will be cleaning up the VM stuff (and perhaps some of the VFS stuff) soon. Probably will not make it into 2.2-RELEASE though. The messages are indicating potential problems that have been generally checked out. The problem is that it requires careful consideration/coordination to clean-em up. John