From 0df8c0816baebe641765d748a3053bc873311ece Mon Sep 17 00:00:00 2001
From: Daniel Dunbar <daniel@zuster.org>
Date: Fri, 22 Aug 2008 20:18:22 +0000
Subject: [PATCH] Add some QA related example clang projects.

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@55196 91177308-0d34-0410-b5e6-96231b3b80d8
---
 www/get_involved.html | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/www/get_involved.html b/www/get_involved.html
index 712c0e73bb..efbba1031e 100644
--- 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
 LLVM.</li>
 
+<li><b>Self-testing using clang</b>: There are several neat ways to
+improve the quality of clang by self-testing. Some examples:
+<ul>
+  <li>Improve the reliability of AST printing and serialization by
+  ensuring that the AST produced by clang on an input doesn't change
+  when it is reparsed or unserialized.
+
+  <li>Improve parser reliability and error generation by automatically
+  or randomly changing the input checking that clang doesn't crash and
+  that it doesn't generate excessive errors for small input
+  changes. Manipulating the input at both the text and token levels is
+  likely to produce interesting test cases.
+</ul>
+</li>
+
 </ul>
 
 <p>If you hit a bug with clang, it is very useful for us if you reduce the code
-- 
2.40.0