summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDaniel Dunbar <daniel@zuster.org>2008-08-22 20:18:22 +0000
committerDaniel Dunbar <daniel@zuster.org>2008-08-22 20:18:22 +0000
commit9f92361f80f7aa51267670f7ac4b496e8556fdab (patch)
treed592f95f75b302f5592f5977da3f0514fb4f1c8a
parent04968da4604a146537f695aee1e88af4f9bc8097 (diff)
downloadbcm5719-llvm-9f92361f80f7aa51267670f7ac4b496e8556fdab.tar.gz
bcm5719-llvm-9f92361f80f7aa51267670f7ac4b496e8556fdab.zip
Add some QA related example clang projects.
llvm-svn: 55196
-rw-r--r--clang/www/get_involved.html15
1 files changed, 15 insertions, 0 deletions
diff --git a/clang/www/get_involved.html b/clang/www/get_involved.html
index 712c0e73bb3..efbba1031e2 100644
--- a/clang/www/get_involved.html
+++ b/clang/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
OpenPOWER on IntegriCloud