Re: what is cooking in sparse-next-20170805

[Luc Van Oostenryck <luc.vanoostenryck@gmail.com>]

On Sat, Aug 05, 2017 at 08:42:12AM -0400, Christopher Li wrote:
> Two new series from Luc has been applied.
> - fix: give a type to bad conditionnal expressions
>   I confirm the wine source file checking went from 23s to 3.x seconds.
> 
> - fix list corruption with recursive remove_usage()
>    this replace 7d54acb0d6d4a9dff3c91688b0223cd4c4a6d6ea
>    "Let pseudo->users loop on duplicate versin of list"
> 
> The kernel compile check shows that has output difference in 3 files
> compare to rc4. I include the diff here. I will dig a bit more which change
> cause it. It seems reasonable enough.  There is one context imbalance
> warning was gone. My guess is that the conditional expression patch
> make sparse understand the source code better now.

Yes.

Also the context checking warnings are quite sensitive to
small changes in the optimization (via the merging of BBs).
But then it's just a change in the file:line:pos, like in
the first file here under. The other two are different and
I also think they are due to the cond-expr change.

-- Luc