From owner-freebsd-toolchain@FreeBSD.ORG Sun Nov 6 20:33:16 2011 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id A18FF1065702; Sun, 6 Nov 2011 20:33:16 +0000 (UTC) Date: Sun, 6 Nov 2011 20:33:16 +0000 From: Alexander Best To: Ed Schouten Message-ID: <20111106203316.GA73216@freebsd.org> References: <20111105102102.GA54596@freebsd.org> <20111106172835.GO2258@hoeg.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111106172835.GO2258@hoeg.nl> Cc: freebsd-toolchain@freebsd.org Subject: Re: [poc] buildkernel + clang + -Werror X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Nov 2011 20:33:16 -0000 On Sun Nov 6 11, Ed Schouten wrote: > Hello Alexander! > > Even though that I agree that Clang is sometimes a bit picky, we'd > better spend the time fixing the actual bugs in the code. I am more than > willing to commit patches that fix actual warnings/errors in code. the problem is, something like uint x; if (x < 0) ... clang will warn about this, yet it is 100% valid code so my vote would be to make such an error into a warning. the same with int x; x = x; i believe in both cases clang is too picky. cheers. alex > > -- > Ed Schouten > WWW: http://80386.nl/