From: Chris Lattner <sabre@nondot.org>
Date: Sun, 24 Aug 2008 05:42:07 +0000 (+0000)
Subject: codegen is still not 'finished', but in a better state than before.
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=3e820afa3a581949e56a30c1ecda976035843e83;p=clang

codegen is still not 'finished', but in a better state than before.


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

diff --git a/www/comparison.html b/www/comparison.html
index 0fb5043ea1..e5ed8e43a9 100644
--- a/www/comparison.html
+++ b/www/comparison.html
@@ -53,9 +53,8 @@
     <li>GCC front-ends are very mature and already support C/C++/ObjC and all
         the variants we are interested in.  clang's support for C++ in
         particular is nowhere near what GCC supports.</li>
-    <li>GCC's codegen is much more mature than clang's right now.  clang is
-        only capable of codegen for small and simple projects and does not yet
-        support debug info. GCC also supports more targets than LLVM.</li>
+    <li>GCC's codegen is much more mature than clang's right now and supports 
+        more targets than LLVM.</li>
     <li>GCC is popular and widely adopted.</li>
     <li>GCC does not require a C++ compiler to build it.</li>
     </ul>