From patchwork Tue Sep 27 16:58:33 2011
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [wwwdocs] Add info about IPA optimization and LTO improvments
From: Gerald Pfeifer <gerald@pfeifer.com>
X-Patchwork-Id: 116634
Message-Id: <alpine.LNX.2.00.1109271857170.8149@gerinyyl.fvgr>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: Andi Kleen <andi@firstfloor.org>, gcc-patches@gcc.gnu.org,
 Martin Jambor <mjambor@suse.cz>
Date: Tue, 27 Sep 2011 18:58:33 +0200 (CEST)

On Tue, 27 Sep 2011, Jan Hubicka wrote:
> thanks for corrections.  This is what I've comitted now.

And here are some markup fixes on top, that address complaints by
the validator.

Gerald

Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/changes.html,v
retrieving revision 1.34
diff -u -r1.34 changes.html
--- changes.html	27 Sep 2011 13:50:27 -0000	1.34
+++ changes.html	27 Sep 2011 16:56:42 -0000
@@ -58,6 +58,7 @@
     was added to allow users to control the cutoff between doing switch statements
     as a series of if statements and using a jump table.
     </li>
+
     <li>Link-time optimization improvements:
     <ul>
       <li>Improved scalability and reduced memory usage.  Link time optimization
@@ -68,8 +69,10 @@
       <li>Streaming performance (both outbound and inbound) has been improved.</li>
       <li><code>ld -r</code> is now supported with LTO.</li>
       <li>Several bug fixes, especially in symbol table handling and merging.</li>
-    </ul>
+    </ul></li>
+
     <li>Interprocedural optimization improvements:
+    <ul>
       <li>Inliner heuristic can now take into account that after inlining
       code will be optimized out because of known values (or properties) of function parameters.
       For example:
@@ -117,9 +120,8 @@
       <code>true</code>, while other with <code>flag</code> being
       <code>false</code>.  This leads to performance improvements previously
       possibly only by inlining all calls.  Cloning causes a lot less code size
-      growth.
-    <ul>
-    </ul>
+      growth.</li>
+    </ul></li>
   </ul>
 
 <h2>New Languages and Language specific improvements</h2>