linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alexey Zaytsev" <alexey.zaytsev@gmail.com>
To: Derek M Jones <derek@knosof.co.uk>
Cc: Josh Triplett <josh@kernel.org>, linux-sparse@vger.kernel.org
Subject: Re: Sparse and the Google Summer of Code 2008
Date: Wed, 12 Mar 2008 05:20:54 +0300	[thread overview]
Message-ID: <f19298770803111920s1e23143dia70e7118f0a16c20@mail.gmail.com> (raw)
In-Reply-To: <47D734C2.1020903@knosof.co.uk>

On 3/12/08, Derek M Jones <derek@knosof.co.uk> wrote:
> Josh,
>
>
>  >> I know, last year was not all that successful, but maybe
>  >> there will be more applications this year. I've got some
>  >> ideas about abstract interpretation for one. I can't promise
>  >> that I'll choose sparse, there should be lots of interesting
>  >> projects this year, but there are other people as well.
>  >
>  > At least one other person has asked about Sparse and SoC, which
>  > suggests that some interest exists.  I'll work on getting the
>  > org forms filled out today.
>  >
>  > If anyone else on the Sparse list has an interest in mentoring, please
>  > let me know as soon as possible.
>
>
> The ideas so far proposed are major undertakings.  The sort of
>  thing a summer student will only scratch the surface of.
>
I have nothing against adding more easier projects, but please
keep the proposed ones. ;)

>  I think it would be useful to analyze the Linux bug history,
>  looking for known faults and their fixes, that are currently not
>  detected by Sparse, but which look like they are amenable to static
>  detection.
>  If more faults are required there is always the BSD bug list.
>
>  If the existing faults were categorized it would give some idea
>  of the kinds of constructs that ought to be searched for.
>
>  --
>  Derek M. Jones                              tel: +44 (0) 1252 520 667
>  Knowledge Software Ltd                      mailto:derek@knosof.co.uk
>  Applications Standards Conformance Testing    http://www.knosof.co.uk
>
> --
>  To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
>  the body of a message to majordomo@vger.kernel.org
>  More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2008-03-12  2:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 17:38 Sparse and the Google Summer of Code 2008 Alexey Zaytsev
2008-03-11 18:20 ` Josh Triplett
2008-03-11 19:08   ` James Westby
2008-03-11 22:10   ` Christopher Li
2008-03-12  1:41   ` Derek M Jones
2008-03-12  2:20     ` Alexey Zaytsev [this message]
2008-03-12  4:28     ` Josh Triplett
2008-03-12 15:19       ` Neil Booth
2008-03-12 20:01         ` Josh Triplett

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=f19298770803111920s1e23143dia70e7118f0a16c20@mail.gmail.com \
    --to=alexey.zaytsev@gmail.com \
    --cc=derek@knosof.co.uk \
    --cc=josh@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).