Newer
Older
<!-- Consulted: http://www.w3.org/TR/CSS1 & http://www.w3.org/TR/CSS21/ & http://www.w3.org/TR/html401/ -->
Kevin
committed
<!-- Material used from: HTML 4.01 specs: http://www.w3.org/TR/html401/ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
Kevin
committed
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<title>Clang - Get Involved</title>
<link type="text/css" rel="stylesheet" href="menu.css" />
<link type="text/css" rel="stylesheet" href="content.css" />
</head>
<body>
<!--#include virtual="menu.html.incl"-->
<div id="content">
<h1>Getting Involved</h1>
There are many tasks that are open to new developers who want to get involved with the Clang project. Below, you will find details on how to get started with Clang, plus a few tasks that we need help with.<br>
<br>
Please note that the information provided here is not completely thorough. This is intentional. If you plan to work on Clang, we would like you to get involved with the other developers. This will allow us to work together better and will give you a better feel for how things are done.
You can talk with other developers at the following mailing list: <a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev">cfe-dev mailing list</a>.
The clang mailing list is a very friendly place. You can see the archives for records of past discussion. Note that a significant amount of design discussion takes place on the <a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits">cfe-commits mailing list</a>.
<h2>Getting Started</h2>
<h3>A word of warning</h3>
While this work aims to provide a fully functional C/C++/ObjC front-end, it is <em>still very early work</em> and is under heavy development. In particular, there is no real C++ support yet (this is obviously a big project), and C/ObjC support is still missing some features. Some of the more notable missing pieces of C support are:
<ol>
<li>The semantic analyzer does not produce all of the warnings and errors it should.
<li>The LLVM code generator is still very early on. It does not support many important things, like any support for structs and unions. That said, it does handle scalar operations and vectors. clang is not ready to be used as a general purpose C code generator yet.
<li>We don't consider the API to be stable yet, and reserve the right to change fundamental things :)
</ol>
Our plan is to continue chipping away at these issues until C works really well, but we'd love help from other interested contributors.
Clang is a subproject of the <a href="http://llvm.org">LLVM Project</a>, but has
its own mailing lists because the communities have people with different
interests. If you are interested in clang only, these two lists should be all
you need. If you are interested in the LLVM optimizer and code generator,
please consider signing up for <a
href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">llvmdev</a> and <a
href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits">llvm-commits</a>
as well.<br>
<ul>
<li><a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits">cfe-commits</a> - This list is for patch submission/discussion.
<li><a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev">cfe-dev</a> - This list is for everything else clang related.
</ul>
<h3>Building clang / working with the code<a name="build"> </a></h3>
If you would like to check out and build the project, the current scheme is:<br>
<ol>
<li>Check out llvm
<ul>
<li>cd llvm/tools
<li>svn co http://llvm.org/svn/llvm-project/cfe/trunk clang
</ul>
<li>Non-mac users: Paths to system header files are currently hard coded
into the tool; as a result, if clang can't find your system headers,
please follow these instructions:
<ul>
<li>'touch empty.c; gcc -v empty.c -fsyntax-only' to get the path.
<li>change clang/Driver/clang.cpp:606 to include that path
</ul>
<li>Build llvm
<ul>
<li>cd clang
<li>make
</ul>
</ol>
<p>Note that the C front-end uses LLVM, but does not depend on llvm-gcc :)</p>
<p>We will eventually integrate this better as a sub-project, but for now it builds a single tool named 'clang'.<br>
Once llvm is built in this way, you can compile C code.
<h3>Examples of using clang</h3>
The clang driver takes a lot of GCC compatible options, which you can see with 'clang --help'. Here are a few examples:
<!-- Thanks to http://shiflett.org/blog/2006/oct/formatting-and-highlighting-php-code-listings
Site suggested using pre in CSS, but doesn't work in IE, so went for the <pre> tag.
-->
<pre class="code">
$ cat ~/t.c
typedef float V __attribute__((vector_size(16)));
V foo(V a, V b) { return a+b*a; }
Preprocessing:
$ clang ~/t.c -E
# 1 "/Users/sabre/t.c" 1
typedef float V __attribute__((vector_size(16)));
V foo(V a, V b) { return a+b*a; }
Type checking:
$ clang -fsyntax-only ~/t.c
GCC options:
$ clang -fsyntax-only ~/t.c -pedantic
/Users/sabre/t.c:2:17: warning: extension used
typedef float V __attribute__((vector_size(16)));
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
1 diagnostic generated.
Pretty printing from the AST:
$ clang ~/t.c -parse-ast-print
typedef float V __attribute__(( vector_size(16) ));
V foo(V a, V b) {
return a + b * a;
}
LLVM code generation:
$ clang ~/t.c -emit-llvm | llvm-as | opt -std-compile-opts | llvm-dis
define <4 x float> @foo(<4 x float> %a, <4 x float> %b) {
entry:
%mul = mul <4 x float> %b, %a ; <<4 x float>>
[#uses=1]
%add = add <4 x float> %mul, %a ; <<4 x float>>
[#uses=1]
ret <4 x float> %add
}
$ clang ~/t.c -emit-llvm | llvm-as | opt -std-compile-opts | llc -
march=ppc32 -mcpu=g5
..
_foo:
vmaddfp v2, v3, v2, v2
blr
$ clang ~/t.c -emit-llvm | llvm-as | opt -std-compile-opts | llc -
march=x86 -mcpu=yonah
..
_foo:
mulps %xmm0, %xmm1
addps %xmm0, %xmm1
movaps %xmm1, %xmm0
ret
</pre>
<h2>Available tasks</h2>
Here are a few tasks that are currently available for newcomers to work on: