Add some QA related example clang projects.

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

diff --git a/www/get_involved.html b/www/get_involved.html
index 712c0e73bb37ba656f633809606d01f48f719806..efbba1031e26078eb75dc4ab1a2b22b5b5d47e0a 100644 (file)
--- a/www/get_involved.html
+++ b/www/get_involved.html
@@ -139,6 +139,21 @@ machine compiler that lets you embed C code into state machines and generate
 C code.  It would be relatively easy to turn this into a JIT compiler using\r
 LLVM.</li>\r
 \r
+<li><b>Self-testing using clang</b>: There are several neat ways to\r
+improve the quality of clang by self-testing. Some examples:\r
+<ul>\r
+  <li>Improve the reliability of AST printing and serialization by\r
+  ensuring that the AST produced by clang on an input doesn't change\r
+  when it is reparsed or unserialized.\r
+\r
+  <li>Improve parser reliability and error generation by automatically\r
+  or randomly changing the input checking that clang doesn't crash and\r
+  that it doesn't generate excessive errors for small input\r
+  changes. Manipulating the input at both the text and token levels is\r
+  likely to produce interesting test cases.\r
+</ul>\r
+</li>\r
+\r
 </ul>\r
 \r
 <p>If you hit a bug with clang, it is very useful for us if you reduce the code\r