From: simonmar <unknown>
Date: Tue, 18 Dec 2001 13:03:12 +0000 (+0000)
Subject: [project @ 2001-12-18 13:03:12 by simonmar]
X-Git-Tag: Approximately_9120_patches~369
X-Git-Url: http://git.megacz.com/?a=commitdiff_plain;h=7f2a1860ed988629e8c48e74e392aadf83dcf2e2;p=ghc-hetmet.git

[project @ 2001-12-18 13:03:12 by simonmar]
Nuke -O2-for-C, since it can cause gcc to generate incorrect code, and
doesn't seem to help much.  Add a comment about this in the 5.02
release notes, saying you can still use -optc-O2 if you really want
to.

(merged from rev. 1.47.2.3)
---

diff --git a/ghc/docs/users_guide/using.sgml b/ghc/docs/users_guide/using.sgml
index ea97423..015522f 100644
--- a/ghc/docs/users_guide/using.sgml
+++ b/ghc/docs/users_guide/using.sgml
@@ -1192,24 +1192,6 @@ f "2"    = 2
 	</varlistentry>
 
 	<varlistentry>
-	  <term><option>-O2-for-C</option>:</term>
-	  <indexterm><primary>-O2-for-C option</primary></indexterm>
-	  <indexterm><primary>gcc, invoking with -O2</primary></indexterm>
-	  <listitem>
-	    <para>Says to run GCC with <option>-O2</option>, which may
-            be worth a few percent in execution speed.  Don't forget
-            <option>-fvia-C</option>, lest you use the native-code
-            generator and bypass GCC altogether!</para>
-
-	    <para><emphasis>Note: some versions of gcc are known to
-	    have code generation bugs with <option>-O2</option>.  Use
-	    this option at your own risk!  But we'd be keen to here
-	    any reports of whether (a) it works or (b) it improves
-	    performance at all.</emphasis></para>
-	  </listitem>
-	</varlistentry>
-
-	<varlistentry>
 	  <term><option>-Ofile &lt;file&gt;</option>:</term>
 	  <indexterm><primary>-Ofile &lt;file&gt; option</primary></indexterm>
 	  <indexterm><primary>optimising, customised</primary></indexterm>