[cfe-commits] r44884 - /cfe/trunk/www/comparison.html

[Chris Lattner]

Author: lattner
Date: Tue Dec 11 16:29:38 2007
New Revision: 44884

URL: http://llvm.org/viewvc/llvm-project?rev=44884&view=rev
Log:
update pch discussion

Modified:
    cfe/trunk/www/comparison.html

Modified: cfe/trunk/www/comparison.html
URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/www/comparison.html?rev=44884&r1=44883&r2=44884&view=diff

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