Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Christian Eggers <ceggers@arri.de>,
	linux-sparse@vger.kernel.org, Dirk Mueller <dmueller@suse.com>
Subject: Re: Segmentation fault when running sparse with current linux master
Date: Fri, 25 Sep 2020 10:46:46 +0200	[thread overview]
Message-ID: <20200925084646.56wyiphyl65qidwd@ltop.local> (raw)
In-Reply-To: <141c85b6-f607-7594-ed3f-49684fe4bb3a@gmail.com>

On Fri, Sep 25, 2020 at 07:37:57AM +0200, Jiri Slaby wrote:
> On 24. 09. 20, 21:38, Luc Van Oostenryck wrote:
> > 
> > In the official tree, there is a branch 'maint-v0.6.2' which just contain
> > 4 patches fixing some problems with the release v0.6.2, the second patch
> > 	77f35b796cc8 ("generic: fix missing inlining of generic expression")
> > being the one fixing this problem.
> 
> Being fixed in Tumbleweed:
> https://build.opensuse.org/request/show/837254

Awesome! Thank you.
 
> If you want the fix on older distros, we can do that, but you have to
> create a bug against the product first… 20180324 is pretty old version
> and is both in 15.1 and even 15.2.

Mmmm, 20180324, that's sparse v0.5.2. It's very old indeed and
unusable for current kernel development anyway.

Best regards,
-- Luc

      reply	other threads:[~2020-09-25  8:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 11:08 Segmentation fault when running sparse with current linux master Christian Eggers
2020-09-17 14:20 ` Luc Van Oostenryck
2020-09-21  7:44   ` Christian Eggers
2020-09-24 19:38     ` Luc Van Oostenryck
2020-09-25  5:37       ` Jiri Slaby
2020-09-25  8:46         ` 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=20200925084646.56wyiphyl65qidwd@ltop.local \
    --to=luc.vanoostenryck@gmail.com \
    --cc=ceggers@arri.de \
    --cc=dmueller@suse.com \
    --cc=jirislaby@gmail.com \
    --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