Date: Tue, 10 Jun 2003 16:03:18 -0700
From: Dave Olien <dmo@osdl.org>
To: Steven Cole <elenstev@mesatop.com>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sparse type checking on function pointers
Message-ID: <20030610230318.GA10106@osdl.org>
References: <20030610212404.GA25410@osdl.org> <1055284400.2269.56.camel@spc9.esa.lanl.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1055284400.2269.56.camel@spc9.esa.lanl.gov>
User-Agent: Mutt/1.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1326
Lines: 41

On Tue, Jun 10, 2003 at 04:33:20PM -0600, Steven Cole wrote:
>
> That reduced the number of that kind of warning significantly.
> 

Thanks! I'm still kind of groping my way through the code, fixing
these warnings as a motivator to keep me working my way through it.

> 
> Now, if only Linus would change this:
> 
> CHECK           = /home/torvalds/parser/check
> 
> to something more reasonable like
> 
> CHECK           = /usr/local/bin/check
> 
> Steven
> 

I assume Linus has done this because the sparse library is still
a prototype, and the "check" binary is not really the intended end point
but just a simple front-end to invoke the library to test it.

I find it really easy to just over-ride this on the make command line:

	make CHECK=/dmo_local/BK_TREES/sparse_original/check C=1

This makes it easy for me to test different versions of the library as
I'm making modifications either to fix a problem, or to put debug statements
into the source code to undestand it.

Combine this with a good shell that supports history editing, and it's
not really a big problem.

Dave
-
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/