On Mon, Apr 14, 2014 at 06:00:04PM -0700, Josh Triplett wrote: > > and it slows down > > kernel development'. > > No, it doesn't slow down development builds; it makes kernel builds > slower if and only if LTO is turned on, which most kernel developers > won't need to do. On the other hand, distro and embedded kernels can do > so for final builds, and developers pushing to minimize the kernel can LTO inherently is going to slow down development because it does inflate the testing matrix - a developer really should test an LTO build. That said, the increased checking of the source code for validity across compilation units done by the LTO final link is a benefit by itself. With my MIPS maintainer head on I can say it's required fixes / cleanups of several thousand lines which have already been merged several kernel versions ago because they all were beneficial even without LTO. A mere three small commits preparing arch/mips for LTO support and that don't make sense without LTO are remaining. So it's not a support/testing nightmare. And while the code size reduction is less for MIPS than what others have reported for their platforms (I'm still investigating) is still is enough that embedded developers would commit murder for. Ralf -- 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
