ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] coverity, static checking etc.
Date: Fri, 9 May 2014 12:29:57 -0700	[thread overview]
Message-ID: <20140509192956.GB13050@jtriplet-mobl1> (raw)
In-Reply-To: <1399656674.4136.12.camel@jlt4.sipsolutions.net>

On Fri, May 09, 2014 at 07:31:14PM +0200, Johannes Berg wrote:
> On Fri, 2014-05-09 at 10:19 -0700, josh@joshtriplett.org wrote:
> 
> > I'd like to see this topic as well.  I think we could do a lot better
> > here than we do.  And don't forget that GCC is one of our top static
> > analysis tools, if only because it's the only one *everyone* runs; that
> > includes both warnings and the possibility of shipping and building our
> > own GCC plugin.
> > 
> > I'd also like to nominate Christopher Li, for Sparse.
> 
> Seconded, I'm also interested in general in whether people still think
> sparse is useful and we should give it attention, or should focus more
> on really getting everything into gcc - we have a number of sparse
> warnings in very low-level header files that get used everywhere, for
> example the one I just fixed in [1] or the one I tried to fix but that
> ended up being buggy ([2]), but there doesn't seem to be much attention
> to these during the patch submission etc.

I definitely still find Sparse useful and regularly check my own kernel
code with it.  Fengguang Wu's automated build-and-test bot also uses
Sparse.

I *would* like to see more of Sparse's functionality make it into GCC,
so that it gets used as part of default builds.  HPA and I have been
working to document some of the major bits so that GCC can implement
them [1], and Tom Tromey is working on GCC implementations [2].

[1]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59851
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59852
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59855
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59856

[2] https://github.com/tromey/gcc/tree/add-sparse-attributes

- Josh Triplett

  parent reply	other threads:[~2014-05-09 19:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 17:07 Dave Jones
2014-05-09 17:19 ` josh
2014-05-09 17:31   ` Johannes Berg
2014-05-09 17:54     ` Guenter Roeck
2014-05-09 18:04     ` Mark Brown
2014-05-09 19:08     ` Jiri Kosina
2014-05-09 19:41       ` Dmitry Torokhov
2014-05-09 19:29     ` Josh Triplett [this message]
2014-05-09 17:37 ` Bjorn Helgaas
2014-05-09 20:18 ` Arnd Bergmann
2014-05-09 20:33   ` Dave Jones
2014-05-09 21:39     ` Arnd Bergmann
2014-05-09 20:33 ` Roland Dreier
2014-05-09 20:52   ` Dave Jones
2014-05-09 20:57 ` tytso
2014-05-14 11:06   ` Dan Carpenter
2014-05-11 11:10 ` Wolfram Sang
2014-05-12  6:48   ` Michal Simek
2014-05-12  9:32     ` Wolfram Sang
2014-05-14 11:09       ` Dan Carpenter
2014-05-14 13:32       ` Johannes Berg
2014-05-14 13:51         ` Guenter Roeck
2014-05-14 15:22           ` Wolfram Sang
2014-05-14 15:44             ` Peter Huewe
2014-05-14 16:36               ` Wolfram Sang
2014-05-18 16:38     ` Mauro Carvalho Chehab
2014-05-19 10:13       ` Michal Simek
2014-05-12  8:58   ` Peter Senna Tschudin

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=20140509192956.GB13050@jtriplet-mobl1 \
    --to=josh@joshtriplett.org \
    --cc=johannes@sipsolutions.net \
    --cc=ksummit-discuss@lists.linuxfoundation.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