On Sat, Jul 1, 2017 at 2:24 AM, Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> wrote: > > Sure it make some sense. > > But how often it happen and when it happen how much developers > are impacted and for how long? It actually happen right now with the kernel using require_context which is not supported by sparse. Sparse should report error on the sparse related syntax which it does not support. Gcc is no going to report error on those sparse related attributes because gcc never see them. Because we have noway to tell an unknown attribute is belong to sparse or gcc. Sparse checker should report it. It is very bad silence on those sparse specific error and developer have no way to know it. I am fine with other use of sparse like sparse-llvm turn it off by default. But for sparse checker program itself. I think report the error is the right thing to do. As for the distro version of sparse is too old. I think the right thing to do is just get into the habit of release more often. I am guilty of not cutting a release for 3 years. On the other hand, things are getting better now. Thanks to you, sparse has merge more change in the recent half years than all of the two years before it. I do expect to see another release to merge your huge number of patches. Chris -- 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
