On Wed, 21 Sep 2011, Jan Hubicka wrote:
> Index: changes.html
> ===================================================================
> +     <li>Link-time optimization improvements:
> +     <ul>
> +       <li>Improved scalability and reduced memory usage.  Link time 
> optimization
> +       of Firefox now require 3GB of RAM on 64bit system, while over 8GB was 
> needed

"requires"
"on a 64-bit"

> +       previously. Linking time has been improved, too. The serial stage of 
> linking
> +       Firefox binary has been sped up approximately by factor of 10.</li>
> +       <li>Reduced size of object files and temporary storage used during 
> linktime.</li>

"linking"?

> +       <li>Streaming performance has been improved.</li>

Outbound, inbound, or both?

> +       <li>Number of bug fixes, especially in symbol table handling and 
> merging.</li>

"Several bug fixes"

> +       <li>Inliner heuristic can now take into account fact that after 
> inlining
> +       code will be optimized out because of known values (or properties) of 
> function parameters.

Omit "fact".

> +       The call of <code>foo</code> will be inlined into <code>bar</code> 
> even when
> +       optimizing for code size. Constructs based on 
> <code>__builtin_constant_p</code>
> +       are now understood by inliner and code size estimates are evaulated a 
> lot
> +       more realistically.</li>

"by the inliner"
Typo: "evaluated"

> +       <li>Representation of C++ virtual thunks and aliases has been

"The representation"

> +       re-engineered. The aliases no longer pose optimization barriers and 
> calls to an

"C++ aliases" or just "Aliases" if you think the context is sufficiently
clear.

> +       <li>Inter-procedural constant propagation pass has been rewritten.  
> It now performsa

"The inter-procedural"

> +       GCC will now produce two copies of <code>foo</code>. One with 
> <code>flag</code> being
> +       <code>true</code>, while other with <code>flag</code> being
> +       <code>false</code>. 

"...de>, the other with..."

> This leads to preformance improvements previusly

Typo: "performance"

Typo: "previously"

> + possibly only by inlining all calls.  Cloning cause a lot less code 

"causes"


Fine from my perspective modulo the changes above.

I guess I need to dust my old codebase and see how modern GCC fares
in terms of performance. :-)

Gerald

Reply via email to