update pch discussion

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

diff --git a/www/comparison.html b/www/comparison.html
index dd1c36a9c5e7329b01b201ca3945b1187f3a1721..66cdf59e5b9838c80daba5129a413699a93feef3 100644 (file)
--- a/www/comparison.html
+++ b/www/comparison.html
@@ -94,10 +94,11 @@
         example, if you write "x-x" in your source code, the GCC AST will\r
         contain "0", with no mention of 'x'.  This is extremely bad for a\r
         refactoring tool that wants to rename 'x'.</li>\r
-    <li>GCC does not have a way to serialize the AST of a file out to disk and \r
-        read it back into another program.  Its PCH mechanism is architecturally\r
-        only able to read the dump back into the exact same executable as the\r
-        one that produced it.</li>\r
+    <li>Clang can serialize it's AST out to disk and read it back into another \r
+        program, which is useful for whole program analysis.  GCC does not have\r
+        this, but its current PCH mechanism is close.  However, GCC's current \r
+        PCH support is architecturally only able to read the dump back into \r
+        the exact same executable as the one that produced it.</li>\r
     <li>Clang is <a href="features.html#performance">much faster and uses far\r
         less memory</a> than GCC.</li>\r
     <li>Clang aims to provide extremely clear and concise diagnostics (error and\r