From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Possible incorrect linearization of code (master branch)
Date: Mon, 6 Mar 2017 18:47:36 +0000 [thread overview]
Message-ID: <CACXZuxd_6YS7cficTeuPayyYCT-0Q==i3hje_Xd-MtoAP6bLyQ@mail.gmail.com> (raw)
In-Reply-To: <20170306163638.huqjg6my2qhwyyzy@macpro.local>
On 6 March 2017 at 16:36, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> 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
next prev parent reply other threads:[~2017-03-06 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 15:22 Possible incorrect linearization of code (master branch) Dibyendu Majumdar
2017-03-06 16:36 ` Luc Van Oostenryck
2017-03-06 18:47 ` Dibyendu Majumdar [this message]
2017-03-06 19:26 ` Luc Van Oostenryck
2017-03-06 22:39 ` Dibyendu Majumdar
2017-03-07 6:42 ` Luc Van Oostenryck
2017-03-07 15:45 ` Christopher Li
2017-03-07 17:13 ` Dibyendu Majumdar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACXZuxd_6YS7cficTeuPayyYCT-0Q==i3hje_Xd-MtoAP6bLyQ@mail.gmail.com' \
--to=mobile@majumdar.org.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).