From: Josh Triplett <josh@kernel.org>
To: Alexey Zaytsev <alexey.zaytsev@gmail.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Sparse and the Google Summer of Code 2008
Date: Tue, 11 Mar 2008 11:20:47 -0700 [thread overview]
Message-ID: <47D6CD7F.6010800@kernel.org> (raw)
In-Reply-To: <f19298770803111038o3655a216vfe5a4b46876e7218@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]
Alexey Zaytsev wrote:
> Is sparse going to participate in this year's soc?
> I e-mailed Josh a day or two ago, but got no answer,
> and the org application deadline is May 12, 12:00 PDT.
>
> 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.
For anyone thinking about project ideas, I'd like to make two general
recommendations:
* Have specific goals, rather than just "improve support for $FOO".
* Release early, release often. Please get comfortable with the idea
of releasing your work to the Sparse mailing list, regardless of the
current state of that work.
Regarding specific project ideas, I would have a particularly strong
interest in projects related to improved context checking (including
via abstract interpretation or similar), projects to make it easier to
add new checks to Sparse or maintain the existing checks, or projects
attempting to port C test suites (such as GCC's) to Sparse.
(In that last case, many tests will not apply due to the lack of code
generation, but if you want to write a code eneration backend do feel
free. :) Also, many tests would still not apply due to lack of
specific optimizations.)
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2008-03-11 18:27 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 [this message]
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
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=47D6CD7F.6010800@kernel.org \
--to=josh@kernel.org \
--cc=alexey.zaytsev@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;
as well as URLs for NNTP newsgroup(s).