From: Chris Lattner <sabre@nondot.org>
Date: Sun, 27 Jul 2008 06:10:19 +0000 (+0000)
Subject: list delta and distcc.
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=59f0a32147d2c9e6c41b134bfbc72cf5dc4b35ec;p=clang

list delta and distcc.


git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@54120 91177308-0d34-0410-b5e6-96231b3b80d8
---

diff --git a/www/get_involved.html b/www/get_involved.html
index c3c7c809bb..398a1151e5 100644
--- a/www/get_involved.html
+++ b/www/get_involved.html
@@ -124,6 +124,15 @@ source code. The advantage of using Clang for such a tool is that the tool would
 use the same preprocessor/parser/ASTs as the compiler itself, giving it a very
 rich understanding of the code.</li> </ul>
 
+<li><b>Use clang libraries to implement better versions of existing tools</b>:
+Clang is built as a set of libraries, which means that it is possible to
+implement capabilities similar to other source language tools, improving them
+in various ways.  Two examples are <a href="http://distcc.samba.org/">distcc</a>
+and the <a href="http://delta.tigris.org/">delta testcase reduction tool</a>.
+The former can be improved to scale better and be more efficient.  The later
+could also be faster and more efficient at reducing C-family programs if built
+on the clang preprocessor.</li>
+
 <p>If you hit a bug with clang, it is very useful for us if you reduce the code
 that demonstrates the problem down to something small.  There are many ways to
 do this; ask on cfe-dev for advice.</p>