X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fusing.xml;h=115c290491f97c61f766e70ef4f35636c2180502;hb=3bb700d515de2405fa5db3326482e529f332d508;hp=cc5045e1b9fd580d527d7098c65db9217c01127e;hpb=4b7d8ae0cdf92b0d8789676a4be89b41a4582472;p=ghc-hetmet.git

diff --git a/docs/users_guide/using.xml b/docs/users_guide/using.xml
index cc5045e..115c290 100644
--- a/docs/users_guide/using.xml
+++ b/docs/users_guide/using.xml
@@ -1312,13 +1312,15 @@ f foo = foo { x = 6 }
             <literal>import</literal> declaration
 	    that does not explicitly list the entities brought into scope. For 
 	    example
+      </para>
 <programlisting>
 module M where
   import X( f )
   import Y
   import qualified Z
   p x = f x x
-<programlisting>
+</programlisting>
+        <para>
           The <option>-fwarn-import-lists</option> flag will warn about the import
 	  of <literal>Y</literal> but not <literal>X</literal>
 	  If module <literal>Y</literal> is later changed to export (say) <literal>f</literal>,
@@ -1326,6 +1328,7 @@ module M where
 	  ambiguous.  No warning is produced for the import of <literal>Z</literal>
 	  because extending <literal>Z</literal>'s exports would be unlikely to produce
 	  ambiguity in <literal>M</literal>.
+        </para>
 	</listitem>
       </varlistentry>
 
@@ -1370,6 +1373,20 @@ module M where
       </varlistentry>
 
       <varlistentry>
+	<term><option>-fwarn-missing-local-sigs</option>:</term>
+	<listitem>
+	  <indexterm><primary><option>-fwarn-missing-local-sigs</option></primary></indexterm>
+	  <indexterm><primary>type signatures, missing</primary></indexterm>
+
+	  <para>If you use the
+          <option>-fwarn-missing-local-sigs</option> flag GHC will warn
+          you about any polymorphic local bindings. As part of
+	    the warning GHC also reports the inferred type. The
+          option is off by default.</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
 	<term><option>-fwarn-name-shadowing</option>:</term>
 	<listitem>
 	  <indexterm><primary><option>-fwarn-name-shadowing</option></primary></indexterm>
@@ -1698,7 +1715,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.)
@@ -2200,27 +2217,6 @@ f "2"    = 2
         </listitem>
       </varlistentry>
 
-      <varlistentry>
-	<term><option>-monly-[32]-regs</option>:</term>
-	<listitem>
-	  <para>(x86 only)<indexterm><primary>-monly-N-regs
-          option (iX86 only)</primary></indexterm> GHC tries to
-          &ldquo;steal&rdquo; four registers from GCC, for performance
-          reasons; it almost always works.  However, when GCC is
-          compiling some modules with four stolen registers, it will
-          crash, probably saying:
-
-<screen>
-Foo.hc:533: fixed or forbidden register was spilled.
-This may be due to a compiler bug or to impossible asm
-statements or clauses.
-</screen>
-
-          Just give some registers back with
-          <option>-monly-N-regs</option>.  Try `3' first, then `2'.
-          If `2' doesn't work, please report the bug to us.</para>
-	</listitem>
-      </varlistentry>
     </variablelist>
 
   </sect1>