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
Date: Wed, 8 Jul 2020 12:43:50 +0200 [thread overview]
Message-ID: <20200708104350.j2d3tz2udin2mqlw@ltop.local> (raw)
In-Reply-To: <20200708095904.GI2549@kadam>
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
prev parent reply other threads:[~2020-07-08 10:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 0:06 Sparse improvements & regressions for Linux v5.7-rc1 -> v5.8-rc1 Luc Van Oostenryck
2020-07-08 9:59 ` Dan Carpenter
2020-07-08 10:43 ` Luc Van Oostenryck [this message]
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=20200708104350.j2d3tz2udin2mqlw@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
/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).