On Sun, Feb 03, 2013 at 01:21:13PM +0800, Zheng Liu wrote: > 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. :-( > > Yes, this problem has been reported by Fengguang. So I am plan to use > another method to define extent_status structure as last time we > discuessed. What do you think? > I don't get this warning on my version of Sparse. Sparse used to assume -m32 all the time but now that's been changed. Are you using the most recent version of Sparse? Try passing -m64. regards, dan carpenter -- 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
