Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 8 Jul 2020 12:43:50 +0200
From:   Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To:     Dan Carpenter <dan.carpenter@oracle.com>
Cc:     linux-sparse@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Sparse improvements & regressions for Linux v5.7-rc1 -> v5.8-rc1
Message-ID: <20200708104350.j2d3tz2udin2mqlw@ltop.local>
References: <20200708000651.f5bykhd3mhgsbvk7@ltop.local>
 <20200708095904.GI2549@kadam>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200708095904.GI2549@kadam>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Jul 08, 2020 at 12:59:04PM +0300, Dan Carpenter wrote:
> On Wed, Jul 08, 2020 at 02:06:51AM +0200, Luc Van Oostenryck wrote:
> > I've finally written a silly script to easily compare my tests
> > of Sparse on the kernel. So, it's now easy to share those results.
> > 
> > It's a comparison of Sparse's unique warnings between v5.7-rc1 &
> > v5.8-rc1 on x86-64 (defconfig + allyesconfig). The results are
> > quite similar on other architectures.
> > 
> > Note that the differences can be caused by changes in the kernel
> > code or in Sparse code.
> > 
> > Have fun.
> > 
> 
> This is quite fun!  Could you post the raw errors from the v5.8-rc1
> kernel as well?  Probably it's too big for LKML, so it would have to
> be posted to pastebin or something.

Yes, even compressed it's too big.
I've added them in my dev tree on github:
	https://github.com/lucvoo/sparse-dev/commits/logs
It's just the last commit in the subdirectory 'Logs'.
I've added the raw and the cooked form.

Have fun,
-- Luc