-<!-- Consulted: http://www.w3.org/TR/CSS1 & http://www.w3.org/TR/CSS21/ & http://www.w3.org/TR/html401/ -->\r
-<!--\r
-Consulted:\r
-HTML 4.01 specs: http://www.w3.org/TR/html401/\r
--->\r
-<head>\r
- <title>Clang - Get Involved</title>\r
- <link type="text/css" rel="stylesheet" href="menu.css" />\r
- <link type="text/css" rel="stylesheet" href="content.css" />\r
-</head>\r
-<body>\r
-<!--#include virtual="menu.html.incl"-->\r
-<div id="content">\r
-<h1>Getting Involved</h1>\r
-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>\r
-<br>\r
-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.\r
-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>. (On the other hand, if you feel uncomfortable getting involved in a public mailing list right away, and you just want to ask a few questions to begin with, then you can contact Chris personally, until you feel comfortable moving to the mailing list.)\r
-\r
-<h2>Getting Started</h2>\r
-<h3>A word of warning</h3>\r
-While this work aims to provide a fully functional C/C++/ObjC front- end, it is *still very early work*. 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:\r
-<ol>\r
- <li>The semantic analyzer does not produce all of the warnings and errors it should.\r
- <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.\r
- <li>We don't consider the API to be stable yet, and reserve the right to change fundamental things :)\r
-</ol>\r
-Our plan is to continue chipping away at these issues until C works really well, but we'd love help from other interested contributors.\r
-<h3>Follow what's going on</h3>\r
-To avoid spamming the main LLVM mailing list, two lists were setup just for Clang. Please take all Clang related discussion to these two lists. (Note: If all you care about is the Clang front-end, and not the overall LLVM Compiler project, then the two CFE lists are all that you need.)<br>\r
-<ul>\r
-<li><a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits">cfe-commits</a> - This list is for patch submission/discussion.\r
-<li><a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev">cfe-dev</a> - This list is for everything else clang related.\r
-</ul>\r
-<h3>Building clang / working with the code<a name="build"> </a></h3>\r
-If you would like to check out and build the project, the current scheme is:<br>\r
-<ol>\r
- <li>Check out llvm\r
- <ul>\r
- <li>cd llvm/tools\r
- <li>svn co http://llvm.org/svn/llvm-project/cfe/trunk clang\r
- </ul>\r
- <li>Non-mac users: Paths to system header files are currently hard coded into the tool; as a result, non-Mac users will need to change the path in one of the files.\r
- <ul>\r
- <li>'touch empty.c; gcc -v empty.c -fsyntax-only' to get the path.\r
- <li>change clang/Driver/clang.cpp:606 to include that path\r
- </ul>\r
- <li>Build llvm\r
- <ul>\r
- <li>cd clang\r
- <li>make\r
- </ul>\r
-</ol>\r
-<p>Note that the C front-end uses libsupport and libsystem. You don't need llvm-gcc :)\r
-<p>We will eventually integrate this better as a sub-project, but for now it builds a single tool named 'clang'.<br>\r
-Once llvm is built in this way, you can compile C code.\r
-<h3>Examples of using clang</h3>\r
-The clang driver takes a lot of GCC compatible options, which you can see with 'clang --help'. Here are a few examples:\r
-<!-- Thanks to http://shiflett.org/blog/2006/oct/formatting-and-highlighting-php-code-listings\r
- Site suggested using pre in CSS, but doesn't work in IE, so went for the <pre> tag.\r
--->\r
-<pre class="code">\r
-$ cat ~/t.c\r
-\r
-typedef float V __attribute__((vector_size(16)));\r
-V foo(V a, V b) { return a+b*a; }\r
-\r
-\r
-Preprocessing:\r
-$ clang ~/t.c -E\r
-# 1 "/Users/sabre/t.c" 1\r
-\r
-typedef float V __attribute__((vector_size(16)));\r
-\r
-V foo(V a, V b) { return a+b*a; }\r
-\r
-\r
-Type checking:\r
-$ clang -fsyntax-only ~/t.c\r
-\r
-\r
-GCC options:\r
-$ clang -fsyntax-only ~/t.c -pedantic\r
-/Users/sabre/t.c:2:17: warning: extension used\r
-typedef float V __attribute__((vector_size(16)));\r
- ^\r
-1 diagnostic generated.\r
-\r
-\r
-\r
-Pretty printing from the AST:\r
-$ clang ~/t.c -parse-ast-print\r
-typedef float V __attribute__(( vector_size(16) ));\r
-\r
-V foo(V a, V b) {\r
- return a + b * a;\r
-}\r
-\r
-\r
-LLVM code generation:\r
-$ clang ~/t.c -emit-llvm | llvm-as | opt -std-compile-opts | llvm-dis\r
-define <4 x float> @foo(<4 x float> %a, <4 x float> %b) {\r
-entry:\r
- %mul = mul <4 x float> %b, %a ; <<4 x float>> \r
-[#uses=1]\r
- %add = add <4 x float> %mul, %a ; <<4 x float>> \r
-[#uses=1]\r
- ret <4 x float> %add\r
-}\r
-$ clang ~/t.c -emit-llvm | llvm-as | opt -std-compile-opts | llc - \r
-march=ppc32 -mcpu=g5\r
-..\r
-_foo:\r
- vmaddfp v2, v3, v2, v2\r
- blr\r
-$ clang ~/t.c -emit-llvm | llvm-as | opt -std-compile-opts | llc - \r
-march=x86 -mcpu=yonah\r
-..\r
-_foo:\r
- mulps %xmm0, %xmm1\r
- addps %xmm0, %xmm1\r
- movaps %xmm1, %xmm0\r
- ret\r
-</pre>\r
-<h2>Available tasks</h2>\r
-Here are a few tasks that are currently available for newcomers to work on:\r
-\r
-<h2>Final words</h2>\r
-In any case, we welcome questions, comments, and especially patches :).\r
-<br><br>\r
-Thanks!\r
-<br><br>\r
--Chris\r
-</div>\r
-</body>\r
-</html>
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
+ "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <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 with the Clang Project</h1>
+
+<p>Once you have <a href="get_started.html">checked out and built</a> clang and
+played around with it, you might be wondering what you can do to make it better
+and contribute to its development. Alternatively, maybe you just want to follow
+the development of the project to see it progress.
+</p>
+
+<h2>Contribute</h2>
+
+See the <a href="hacking.html">hacking</a> document for information on how
+to author patches.
+
+<h2>Follow what's going on</h2>
+
+<p>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. The two clang lists are:</p>
+
+<ul>
+<li><a href="http://lists.llvm.org/mailman/listinfo/cfe-commits">cfe-commits
+</a> - This list is for patch submission/discussion.</li>
+
+<li><a href="http://lists.llvm.org/mailman/listinfo/cfe-dev">cfe-dev</a> -
+This list is for everything else Clang related (questions and answers, design
+discussions, etc).</li>
+
+</ul>
+
+<p>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.llvm.org/mailman/listinfo/llvm-dev">llvm-dev</a> and <a
+href="http://lists.llvm.org/mailman/listinfo/llvm-commits">llvm-commits</a>
+as well.</p>
+
+
+<p>The best way to talk with other developers on the project is through the <a
+href="http://lists.llvm.org/mailman/listinfo/cfe-dev">cfe-dev mailing
+list</a>. The clang mailing list is a very friendly place and we welcome
+newcomers. In addition to the cfe-dev list, a significant amount of design
+discussion takes place on the <a
+href="http://lists.llvm.org/mailman/listinfo/cfe-commits">cfe-commits mailing
+list</a>. All of these lists have archives, so you can browse through previous
+discussions or follow the list development on the web if you prefer.</p>
+
+<p>You can also follow the <a href="http://planet.clang.org/">Planet Clang</a>
+community news feed which offers a window into the world, work and lives of
+Clang developers, contributors and the standards they implement.</p>
+
+<p>If you're looking for something to work on, check out our <a
+href="OpenProjects.html">Open Projects</a> page or look through the <a
+href="http://llvm.org/bugs/">Bugzilla bug database</a>.</p>
+
+<h2 id="criteria">Contributing Extensions to Clang</h2>
+
+<p>Clang has always been designed as a platform for experimentation,
+allowing programmers to easily extend the compiler to support great
+new language features and tools. At some point, the authors of these
+extensions may propose that the extensions become a part of Clang
+itself, to benefit the whole Clang community. But not every idea--not
+even every great idea--should become part of Clang. Extensions
+(particularly language extensions) pose a long-term maintenance burden
+on Clang, and therefore the benefits of the extension must outweight
+those costs. Hence, these are the seven criteria used to evaluate the
+merits of a proposed extension:</p>
+
+<ol>
+ <li>Evidence of a significant user community: This is based on a number of factors, including an actual, existing user community, the perceived likelihood that users would adopt such a feature if it were available, and any "trickle-down" effects that come from, e.g., a library adopting the feature and providing benefits to its users.</li>
+
+ <li>A specific need to reside within the Clang tree: There are some extensions that would be better expressed as a separate tool, and should remain as separate tools even if they end up being hosted as part of the LLVM umbrella project.</li>
+
+ <li>A complete specification: The specification must be sufficient to understand the design of the feature as well as interpret the meaning of specific examples. The specification should be detailed enough that another compiler vendor could conceivably implement the feature.</li>
+
+ <li>Representation within the appropriate governing organization: For extensions to a language governed by a standards committee (C, C++, OpenCL), the extension itself must have an active proposal and proponent within that committee and have a reasonable chance of acceptance. Clang should drive the standard, not diverge from it. This criterion does not apply to all extensions, since some extensions fall outside of the realm of the standards bodies.</li>
+
+ <li>A long-term support plan: Contributing a non-trivial extension to Clang implies a commitment to supporting that extension, improving the implementation and specification as Clang evolves. The capacity of the contributor to make that commitment is as important as the commitment itself.</li>
+
+ <li>A high-quality implementation: The implementation must fit well into Clang's architecture, follow LLVM's coding conventions, and meet Clang's quality standards, including high-quality diagnostics and rich AST representations. This is particularly important for language extensions, because users will learn how those extensions work through the behavior of the compiler.</li>
+
+ <li>A proper test suite: Extensive testing is crucial to ensure that the language extension is not broken by ongoing maintenance in Clang. The test suite should be complete enough that another compiler vendor could conceivably validate their implementation of the feature against it.</li>
+</ol>
+
+</div>
+</body>
+</html>
projects / clang / blobdiff