This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [WWWDOCS] Document IPA/LTO/FDO/i386 changes in GCC-4.9


> > +      <li>Functions are no longer pointlessly renamed.</li>
> 
> Readers may struggle a bit with this.  What does it refer to?

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.

I am attaching the changes I comitted.

I dropped this from news changes.  In meantime we merged in the change enabling
slim LTO files by defualt, what about:

Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.9/changes.html,v
retrieving revision 1.41
diff -c -p -r1.41 changes.html
*** changes.html	28 Nov 2013 15:05:51 -0000	1.41
--- changes.html	28 Nov 2013 16:53:37 -0000
***************
*** 15,20 ****
--- 15,25 ----
  <h2>Caveats</h2>
  
    <ul>
+     <li>Because <code>-fno-fat-lto-objects</code> is now by default,
+ 	<code>gcc-ar</code> and <code>gcc-nm</code> wrappers needs
+ 	to be used to handle objects compiled with <code>-flto</code>.
+ 	Additionally the resulting binary needs to be linked with
+ 	<code>-flto</code> (and appropriate optimization flags).</li>
      <li><p>Support for a number of older systems and recently
      unmaintained or untested target ports of GCC has been declared
      obsolete in GCC 4.9.  Unless there is activity to revive them, the
***************
*** 45,50 ****
--- 50,61 ----
      </li>
      <li>Link-time optimization (LTO) improvements:
      <ul>
+       <li>Slim LTO objects are now used by default.  This means that with
+ 	  <code>-flto</code> GCC will no longer produce non-LTO optimized binary
+ 	  in addition to storing object representation in the intermediate
+ 	  language. Consequently <code>-flto</code> no longer causes everything
+ 	  to be optimized twice (once at compile time and again during link time).
+ 	  This feature can be controlled by <code>-ffat-lto-objects</code>.</li>
        <li>Type merging was rewritten. The new implementation is significantly faster
  	  and uses less memory. 
        <li>Better partitioning algorithm resulting in less streaming during

Attachment: changes
Description: Text document


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]