* roottypes.cs: Rename from tree.cs.

[mono.git] / web / faq

diff --git a/web/faq b/web/faq
index 11392f78fdb197cf32e7553349826e4541fe05c0..9a45337118c2e089c7e98e171087c1c6bb50946f 100644 (file)
--- a/web/faq
+++ b/web/faq
@@ -723,11 +723,11 @@ A: Most of Mono is being written using C#, with only
 
      <li> A multi-platform runtime engine: both a JIT engine and an
           interpreter exist.  The JIT engine runs currently on x86,
-          PowerPC and Sparc systems, while the interpreter works on
+          PowerPC Sparc and S390 systems, while the interpreter works on
           x86, SPARC, StrongARM, s390 and PowerPC systems.  
 
-         The JIT engine is being ported to PowerPC, s390, SPARC and
-          amd64 systems as of this time.
+         The JIT engine is being ported to amd64 systems as of this
+         time. 
 
      <li> Supports Linux, BSD, MacOS, Windows and Solaris at this point.
 
@@ -767,7 +767,9 @@ A: Most of Mono is being written using C#, with only
           Portable.NET's compiler.
 
      <li> Mono's C# compiler has strong error handling and has closer
-          adherence to the specification.
+          adherence to the specification with support for definite
+         assignment (required to generate verifiable IL code) and 
+         CLS conformance checking.
 
      <li> Mono's C# compiler is written in C# which is easier for new
           developers to come in and improve, fix and tune.  The Mono
@@ -799,7 +801,7 @@ A: Most of Mono is being written using C#, with only
           href="tdsclient.html">SQL Server</a>, <a
           href="sqlite.html">SQL Lite</a>, <a
           href="mysql.html">MySQL</a>, <a
-          href="postgresql">PostgresSQL</A>, <a href="oledb.html">Ole
+          href="postgresql.html">PostgresSQL</A>, <a href="oledb.html">Ole
           DB</a> and <a href="odbc.html">ODBC</a>.
 
      <li> Mono includes full LDAP support.
@@ -1345,28 +1347,37 @@ A: This has been done.
 <a name="gcc"></a>
 ** Mono and GCC
 
-Q: Are you working on a GCC front-end to C#? A GCC back-end that will
-   generate CIL images? 
+Q: Are you working on a GCC front-end to C#? 
 
-A: We would love to see a GCC modification that would generate CIL
-   images, but there is nothing at this point.
+A: We are not working on a GCC front-end for C#
 
-   The open64 compiler effort from SGI already has modified GCC to
-   generate a new intermediate language instead of RTL.  This could be
+Q: Will you support C/C++ on the Mono VM?
+
+A:The open64 compiler effort from SGI helps a lot in this direction.
+
+   The Open64 compiler is a modified version of GCC that
+   generates a new intermediate language instead of RTL.  This could be
    the foundation to generate CIL code, and to implement the upcoming
    Managed extensions to C++ from ECMA.
 
+   Open64 (and other derivative forks of GCC) split the gcc front-ends
+   from the backends by using the WHIRL intermediate representation.  
+   Kris has begun the implementation of a translator from WHIRL to CIL.
+
+   So it will be possible to use the GCC compilers to target the CIL.
+
+Q: What about Managed C++?
+
+A: Once a full translator for WHIRL exists, we are interested in
+   looking at expanding the GCC frontends to include extensions for
+   Managed C++.
+
 Q: What about making a front-end to GCC that takes CIL images and
    generates native code?
 
 A: There is no active work on this area, but Mono already provides
    pre-compilation services (Ahead-of-Time compilation).
 
-Q: But would this work around the GPL in the GCC compiler and allow
-   people to work on non-free front-ends?
-
-A: People can already do this by targeting the JVM byte codes (there
-   are about 130 compilers for various languages that target the JVM).
 
 <a name="performance"></a>
 ** Performance