[cfe-dev] Contributing to clang

[Nikola Smiljanic]

I'd just like to add that Clang has many different parts, parser + semantic
analysis, C api, static analyzer, IR generation, ast matchers, tools like
clang-format and clang-modernize. My suggestion would be to find a bug from
the list that you know how to reproduce and think you understand and try to
fix it. You can hunt for FIXMEs in the code but these often assume
familiarity with surrounding code.


On Sun, Aug 17, 2014 at 9:12 AM, Chad Rosier <mcrosier at codeaurora.org>
wrote:

> Anthony,
> Grep the bug list, llvm.org/bugs, and see if anything peeks your interest.
>  You might also consider subscribing to the mailing list
> (http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs).
>
>  HTH,
>   Chad
>
> > Hi all,
> >
> > I've been looking to get involved with clang for a while now. I've
> started
> > looking at the open projects page and was looking for some advice.
> >
> > Clang is something I am really interested in but realize there is a lot
> of
> > getting up to speed, can anyone recommend an area where help is needed
> > that
> > might help me get my feet wet. I would really like to get involved, even
> > if
> > it takes me a long time to produce anything valuable.
> >
> > Thanks,
> > --
> > Anthony
> > _______________________________________________
> > cfe-dev mailing list
> > cfe-dev at cs.uiuc.edu
> > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
> >
>
>
> --
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
> hosted by The Linux Foundation
>
> _______________________________________________
> 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/20140817/19b1c294/attachment.html>