Remove -fvia-C references from the users guide

diff --git a/docs/users_guide/flags.xml b/docs/users_guide/flags.xml
index 3920c8e..1a5e67e 100644 (file)
--- a/docs/users_guide/flags.xml
+++ b/docs/users_guide/flags.xml
@@ -1743,13 +1743,7 @@ phase <replaceable>n</replaceable></entry>
              <entry><option>-fasm</option></entry>
              <entry>Use the native code generator</entry>
              <entry>dynamic</entry>
-             <entry>-fvia-C</entry>
-           </row>
-           <row>
-             <entry><option>-fvia-C</option></entry>
-             <entry>Compile via C</entry>
-             <entry>dynamic</entry>
-             <entry>-fasm</entry>
+             <entry>-fllvm</entry>
            </row>
            <row>
              <entry><option>-fllvm</option></entry>

diff --git a/docs/users_guide/phases.xml b/docs/users_guide/phases.xml
index b48ebe8..6ed8de1 100644 (file)
--- a/docs/users_guide/phases.xml
+++ b/docs/users_guide/phases.xml
@@ -543,21 +543,8 @@ $ cat foo.hspp</screen>
         </term>
         <listitem>
           <para>Use GHC's native code generator rather than
-          compiling via C.  This will compile faster (up to twice as
-          fast), but may produce code that is slightly slower than
-          compiling via C.  <option>-fasm</option> is the default.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term>
-          <option>-fvia-C</option>
-          <indexterm><primary><option>-fvia-C</option></primary></indexterm>
-        </term>
-        <listitem>
-          <para>Compile via C instead of using the native code
-          generator.  This is the default on architectures for which GHC
-          doesn't have a native code generator.</para>
+          compiling via LLVM.
+          <option>-fasm</option> is the default.</para>
         </listitem>
       </varlistentry>
 
@@ -569,8 +556,8 @@ $ cat foo.hspp</screen>
         <listitem>
           <para>Compile via LLVM instead of using the native code
           generator. This will generally take slightly longer than the
-          native code generator to compile but quicker than compiling
-          via C. Produced code is generally the same speed or faster
+          native code generator to compile.
+          Produced code is generally the same speed or faster
           than the other two code generators. Compiling via LLVM
           requires LLVM version 2.7 or later to be on the path.</para>
         </listitem>

diff --git a/docs/users_guide/separate_compilation.xml b/docs/users_guide/separate_compilation.xml
index 9ce971d..ae0e80c 100644 (file)
--- a/docs/users_guide/separate_compilation.xml
+++ b/docs/users_guide/separate_compilation.xml
@@ -461,9 +461,7 @@ $ ghc -c parse/Foo.hs parse/Bar.hs gurgle/Bumble.hs -odir `uname -m`
            <para>Keep intermediate <literal>.hc</literal> files when
            doing <literal>.hs</literal>-to-<literal>.o</literal>
            compilations via C (NOTE: <literal>.hc</literal> files
-           aren't generated when using the native code generator, you
-           may need to use <option>-fvia-C</option> to force them
-           to be produced).</para>
+           are only generated by unregisterised compilers).</para>
          </listitem>
        </varlistentry>
 

diff --git a/docs/users_guide/sooner.xml b/docs/users_guide/sooner.xml
index eb85878..ea3e306 100644 (file)
--- a/docs/users_guide/sooner.xml
+++ b/docs/users_guide/sooner.xml
@@ -163,18 +163,6 @@ should go here!</para>
       </varlistentry>
 
       <varlistentry>
-       <term>Compile via C and crank up GCC:</term>
-       <listitem>
-         <para>The native code-generator is designed to be quick, not
-          mind-bogglingly clever.  Better to let GCC have a go, as it
-          tries much harder on register allocation, etc.</para>
-
-         <para>So, when we want very fast code, we use: <option>-O
-         -fvia-C</option>.</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
        <term>Overloaded functions are not your friend:</term>
        <listitem>
          <para>Haskell's overloading (using type classes) is elegant,

diff --git a/docs/users_guide/using.xml b/docs/users_guide/using.xml
index 06862e7..05f1de4 100644 (file)
--- a/docs/users_guide/using.xml
+++ b/docs/users_guide/using.xml
@@ -1701,7 +1701,7 @@ f "2"    = 2
       <para>We don't use a <option>-O*</option> flag for day-to-day
       work.  We use <option>-O</option> to get respectable speed;
       e.g., when we want to measure something.  When we want to go for
-      broke, we tend to use <option>-O2 -fvia-C</option> (and we go for
+      broke, we tend to use <option>-O2</option> (and we go for
       lots of coffee breaks).</para>
 
       <para>The easiest way to see what <option>-O</option> (etc.)