On Thu, 28 Nov 2013, Jan Hubicka wrote:
> We previously renamed every static function foo into foo.1234 (just as a 
> precaution because other compilation unit may have also function foo). 
> This confuses many thins, so now we do renaming only when we see a 
> conflict.

Ah, I see.  Thanks.

>     <ul>
> +     <li>Because <code>-fno-fat-lto-objects</code> is now by default,

I assume you mean "now on by default" or "now enabled by default"?

> +     <code>gcc-ar</code> and <code>gcc-nm</code> wrappers needs

The...wrappers

needs -> need

Fine with those tweaks.

Gerald

PS: I applied the following fix on top of your last commit.

Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.9/changes.html,v
retrieving revision 1.42
diff -u -3 -p -r1.42 changes.html
--- changes.html        29 Nov 2013 00:46:55 -0000      1.42
+++ changes.html        30 Nov 2013 16:36:44 -0000
@@ -46,7 +46,7 @@
     <li>Link-time optimization (LTO) improvements:
     <ul>
       <li>Type merging was rewritten. The new implementation is significantly 
faster
-         and uses less memory. 
+      and uses less memory.</li>
       <li>Better partitioning algorithm resulting in less streaming during
          link time.</li>
       <li>Early removal of virtual methods reduces the size of object files and
@@ -70,7 +70,7 @@
       <li>Local aliases are introduced for symbols that are known to be
          semantically equivalent across shared libraries improving dynamic
          linking times.</li>
-    </ul>
+    </ul></li>
     <li>Feedback directed optimization improvements:
     <ul>
       <li>Profiling of programs using C++ inline functions is now more 
reliable.</li>

Reply via email to