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:
> Hi,
>> > 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 API.)
>> > 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!
>> Gabor
>>> 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:
>>> Hello,
>>>> 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 know.
>>>> 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.
>> Cheers,
>> Anna and Jordan.
>>> Thank you!
>>>> Gábor Kozár
>> _______________________________________________
>> cfe-dev mailing list
>>cfe-dev at cs.uiuc.edu>>http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev>>> _______________________________________________
> cfe-dev mailing list
>cfe-dev at cs.uiuc.edu>http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20130424/c3f46075/attachment.html>