On Tue, Aug 21, 2012 at 09:49:21AM +0200, Ingo Molnar wrote: > > A lot of the overhead on the larger builds is also some > > specific gcc code that I'm working with the gcc developers on > > to improve. So the 4x extreme case will hopefully go down. > > > > The large builds also currently suffer from too much memory > > consumption. That will hopefully improve too, as gcc improves. > > Are there any LTO build files left around, blowing up the size > of the build tree? Hi Ingo, Joe Mario from Red Hat has been assisting Andi with his LTO work. One of the ideas he had which may help here is to push the LTO granularity down to the directory level. This would allow subsystem maintainers to opt-in and keep the compile overhead consistent across randconfigs as the linker would have a smaller pool of files to deal with. Joe was wondering if he hacked something up for the scheduler directory only, if there was some preferred benchmark tools he could run to verify a performance increase or not? Cheers, Don -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
