From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dibyendu Majumdar Subject: Re: Possible incorrect linearization of code (master branch) Date: Mon, 6 Mar 2017 18:47:36 +0000 Message-ID: References: <20170306163638.huqjg6my2qhwyyzy@macpro.local> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-it0-f52.google.com ([209.85.214.52]:38368 "EHLO mail-it0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932387AbdCFSrn (ORCPT ); Mon, 6 Mar 2017 13:47:43 -0500 Received: by mail-it0-f52.google.com with SMTP id m27so56399060iti.1 for ; Mon, 06 Mar 2017 10:47:37 -0800 (PST) In-Reply-To: <20170306163638.huqjg6my2qhwyyzy@macpro.local> Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Luc Van Oostenryck Cc: Linux-Sparse On 6 March 2017 at 16:36, Luc Van Oostenryck wrote: > On Mon, Mar 06, 2017 at 03:22:19PM +0000, Dibyendu Majumdar wrote: >> main: >> .L2: >> >> 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