search for: lightweightipo

...n get about only 7%~13% improvement. Right. Though GCC 4.7 will offer an option to emit just bytecode in object files. Additionally, the biggest gains we generally observe with LTO is when it's coupled with FDO. And almost always, the biggest wins are in the inliner (http://gcc.gnu.org/wiki/LightweightIpo). > Apart from the LTO, we also have some good idea on link time > optimization. I will open another thread to discuss this later. You may want to look at Diablo (http://diablo.elis.ugent.be/). An optimizing linker that has been around for a while. I'm not sure whether it is still bei...

Hi, Brooks, Since this project is helped by many BSD guys in Taiwan, one of MCLinker's main objectives is make direct contribution to the BSD realm. Please feel free to give us suggestions to make sure we can achieve this goal. Any comments are appreciated. We realized open discussion on the mailing list is necessary, and we hope this thread can be a beginning to openly discuss the project

...It is important to compiler engineers too -- you don't want to wait for more than 20min to hit a breakpoint in debugging a compiler problem :) For this reason, GCC LTO is not used in Google. Instead, the much more scalable solution called LIPO is widely used for CMO: https://gcc.gnu.org/wiki/LightweightIpo. LIPO by design requires PGO. While LIPO is scalable, it has its own limitation that prevents the compiler from maximizing the benefit of CMO. The new design is intended to solve the problem with more very aggressive objectives. The new design is pretty simple and shares the basic principles of LI...

On Fri, Dec 12, 2014 at 1:59 PM, Diego Novillo <dnovillo at google.com> wrote: > On 12/12/14 15:56, Adve, Vikram Sadanand wrote: >> >> I've been asked how LTO in LLVM compares to equivalent capabilities >> in GCC. How do the two compare in terms of scalability? And >> robustness for large applications? > > > Neither GCC nor LLVM can handle our

...vement. > > Right. Though GCC 4.7 will offer an option to emit just bytecode in > object files. Additionally, the biggest gains we generally observe > with LTO is when it's coupled with FDO. And almost always, the > biggest wins are in the inliner > (http://gcc.gnu.org/wiki/LightweightIpo). > > > Apart from the LTO, we also have some good idea on link time > > optimization. I will open another thread to discuss this later. > > You may want to look at Diablo (http://diablo.elis.ugent.be/). An > optimizing linker that has been around for a while. I'm not...