X-Git-Url: http://plrg.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FFAQ.html;h=7294cdd1a4294bbdafc5cdb142202b13d1dbe3e9;hb=94f01db27bd96021cd69e82d8096e121bc672efe;hp=ad97be16b23825a0d617fafcbf3687488dd9ca7e;hpb=860e0b4c950285fcaaefc3c218c9d7276fb609e8;p=oota-llvm.git diff --git a/docs/FAQ.html b/docs/FAQ.html index ad97be16b23..7294cdd1a42 100644 --- a/docs/FAQ.html +++ b/docs/FAQ.html @@ -12,9 +12,9 @@
-llvmc is experimental and isn't really supported. We suggest - using llvm-gcc instead.
-When I compile LLVM-GCC with srcdir == objdir, it fails. Why?
@@ -449,7 +436,9 @@ Stop.What source languages are supported?
@@ -538,10 +527,7 @@ Stop.Currently, there isn't much. LLVM supports an intermediate representation which is useful for code representation but will not support the high level (abstract syntax tree) representation needed by most compilers. There are no - facilities for lexical nor semantic analysis. There is, however, a mostly - implemented configuration-driven - compiler driver which simplifies the task - of running optimizations, linking, and executable generation.
+ facilities for lexical nor semantic analysis.When I compile software that uses a configure script, the configure script @@ -659,7 +645,7 @@ Stop.
Finally, compile the C file:
-% cc x.c +% cc x.c -lstdc++