GCC LTO merged to trunk

A few weeks ago the lto branch of gcc was merged to trunk, and was subsequently released in gcc 4.5. Why was I not notified?? What's wrong with you /prog/, sleeping on the job?

Also doesn't LTO support in almost all mainstream compilers sort of make the 'inline' keyword obsolete? Why would I bother inlining anything ever?

>>5
Now if GCC produced worthwhile/quality code, that might actually mean something. Unfortunately, I doubt this has changed.
The point is more that most major compilers support this now, so I can write a library without manually inlining shit and not worry about the performance issues on any major platform. I can write accessors/mutators for C structs where the definition is actually hidden in the C file, and there's no performance penalty. I don't have to worry about the visibility of anything anymore; header files are back to the way they should be, just public function listings and that's it. No more hacks for performance just to cater to those who used GCC.

>>7
you could already do the same thing with -combine -fwhole-program (with a few caveats)
Those caveats are pretty important. You certainly couldn't compile anything large with this method; the memory requirements were too high. -whopr solves this. It was also extremely slow, and you couldn't do incremental builds this way.