[cfe-dev] Clang Static Analyzer GSoC
kozargabor at gmail.com
Wed Apr 24 17:28:45 PDT 2013
Thank you very much for your replies! I'll talk with my manager, but most
likely I won't be applying this year then.
2013/4/25 Jordan Rose <jordan_rose at apple.com>
> Hi, Gabor. The idea with GSoC is that it's a sort of remote
> internship—but, yes, a full-time internship. While we wouldn't be recording
> hours or anything, we'd expect your work to be commensurate with a
> full-time job. I personally don't think it's a good idea to stack GSoC on
> top of an existing 16-hour internship. Sorry!
> Jordan (and Anna)
> On Apr 24, 2013, at 16:19 , Gábor Kozár <kozargabor at gmail.com> wrote:
> > *You should explain which qualifications would make you a good match
> for this project (for example, experience with clang AST could be one).*
> Basically all that I can think of right now is that I have a fair amount
> of experience using the Clang API, as I have built various tools upon it,
> including a kind of a static analyzer, which primarily uses matchers to
> detect potentially funny code. (You may have noticed that I've also been
> trying to help people struck with a particular problem regarding the Clang
> > *It's hard to answer this question. I would suspect it would take the
> whole summer. If you don't think you'll have time this summer (e.g. you
> have research or another job), you could always work on smaller projects
> now and plan to reapply next summer.
> I do have a job, but it's an internship with just 16 hours per week
> worktime required. I can easily handle an additional 30, maybe even 40
> hours per week.
> The reason why I'm even considering applying now is that I'm not sure
> whether for example my next summer will be any better, but I suspect that
> my worktimes will only increase with time.
> On the other hand, I assume that having patches committed to clang would
> be definitely a point in my favor when it comes to ranking.
> Could you give at least some pointers to the amount of work this would
> require per day or per week? Would I be expected to work nearly full-time
> (40 hours per week)?
> Thank you very much for your reply!
> 2013/4/25 Anna Zaks <ganna at apple.com>
>> On Apr 22, 2013, at 12:09 PM, Gábor Kozár <kozargabor at gmail.com> wrote:
>> I find the Clang Static Analyzer fascinating, and would love to work on
>> it. We've been working on a very simple static analyzer, utilizing Clang's
>> AST matcher library, but I have no experience, nor any knowledge, in
>> symbolic execution analysis, apart from the very basics.
>> Great to hear that you are interested in the Static Analyzer!
>> I studied the list of open projects (
>> http://clang-analyzer.llvm.org/open_projects.html), and I'm fairly
>> confident that I could figure out how to implement a lot of it, like
>> modeling new and delete, and exception handling, based on (what little) I
>> My questions are then:
>> 1) Is working on the Clang Static Analyzer a reasonable GSoC project?
>> Definitely, yes.
>> 2) Do you think it would be possible for me to be accepted to the GSoC
>> program with this project, given my lack of knowledge in the area (symbolic
>> execution analysis)?
>> You should explain which qualifications would make you a good match for
>> this project (for example, experience with clang AST could be one). It is
>> also essential to prepare an in depth proposal of what you plan to achieve
>> and what will be involved in getting it done. Modeling new/delete and
>> exception handling is rather challenging and requires changes to the
>> various parts of the analyzer core.
>> 3) If I were accepted, roughly how much time do you think I would need to
>> spend on this project, on a weekly basis? I need this to decide if it is
>> even reasonable for me to apply.
>> It's hard to answer this question. I would suspect it would take the
>> whole summer. If you don't think you'll have time this summer (e.g. you
>> have research or another job), you could always work on smaller projects
>> now and plan to reapply next summer.
>> Anna and Jordan.
>> Thank you!
>> Gábor Kozár
>> cfe-dev mailing list
>> cfe-dev at cs.uiuc.edu
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev