On 6 March 2017 at 16:36, Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> wrote: > On Mon, Mar 06, 2017 at 03:22:19PM +0000, Dibyendu Majumdar wrote: >> main: >> .L2: >> <entry-point> >> call.64 %r10 <- incr, "abcde" >> setne.32 %r15 <- %r13, $101 >> ret.32 %r15 > > > This is already fixed in commit > https://git.kernel.org/cgit/devel/sparse/sparse.git/commit/?h=sparse-next-20170306&id=b8c268640114d614178d4875fbe0f5e6b53b036b > Okay thanks. I had originally started from the release 0.5 version of Sparse, and applied fixes selectively. Because I have a modified version of Sparse with all global state removed, merging changes is a bit painful as it has be done manually. That is why I have not been tracking sparse-next as I thought it is not yet stable. I have now merged all changes from master. Should I merge sparse-next now or wait for it to be merged into master? Regards Dibyendu -- 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
