From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756386AbZD0ODZ (ORCPT ); Mon, 27 Apr 2009 10:03:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754251AbZD0ODQ (ORCPT ); Mon, 27 Apr 2009 10:03:16 -0400 Received: from smtp.ultrahosting.com ([74.213.174.254]:34161 "EHLO smtp.ultrahosting.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753070AbZD0ODQ (ORCPT ); Mon, 27 Apr 2009 10:03:16 -0400 Date: Mon, 27 Apr 2009 09:52:46 -0400 (EDT) From: Christoph Lameter X-X-Sender: cl@qirst.com To: "Eric W. Biederman" cc: David Miller , linux-kernel@vger.kernel.org Subject: Re: [rfc] built-in native compiler for Linux? In-Reply-To: Message-ID: References: <20090422085828.GA16917@elte.hu> <20090424.222952.83381016.davem@davemloft.net> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 25 Apr 2009, Eric W. Biederman wrote: > If this was about teaching sparse to run lockdep at compile time, or > generally about making the kernel compilation much faster and able to > catch many more bugs there might be a point where the effort is worth > the investment. The preprocessor and its interaction with regular C code is quite nasty. If sparse could get rid of the complexities and idiosyncrasies at that level then it may be useful as a "pre" compiler.