On Sat, Feb 02, 2013 at 10:03:43PM -0500, Theodore Ts'o wrote:
> On Wed, Jan 30, 2013 at 10:43:33AM +0800, Zheng Liu wrote:
> >
> > Clang is first coming in my mind. I know that some one try to use it
> > to build a linux kernel and get a lot of problems that are about gcc
> > extension. But for us it seems that things are not too bad. ;)
>
> Clang accepts bitfields with "unsigned long long", but I've discovered
> something which does _not_ support unsigned long long --- the "sparse"
> tool. :-(
>
> I discovered this when running "make C=1", i.e.:
>
> rm -f fs/ext4/extents_status.o
> make C=1 fs/ext4/extents_status.o
Small hint...
If you use:
make C=2 fs/ext4/extents_status.o
Then kbuild will run sparse on all targets you specify,
even if they do not need to be rebuild.
In other words - you then do not need to delete the .o file first.
This works for all the usual ways you can specify a target so to
check all of ext4 you just issue:
make C=2 fs/ext4/
Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
