Nicholas Piggin <npiggin@xxxxxxxxx> writes: >> >> I think we should aim for gc-sections to be used by default and have LTO >> as a possible option only. > > I agree after it starts getting implemented and debugged by small > system users, we could make it default in the interest of sharing > testing and reducing combinations. >From what i understand the main drawback in the past was is that various linker versions become very slow with thousands of sections. So it may cost you built time. For a special small build it's probably ok, but you wouldn't want to make it default. Also usually it's only useful without modules because if you use modules EXPORT_SYMBOL pulls in a lot of unused functions. BTW I'm still maintaining a "real LTO" patchkit here, which has some users (mainly for binary size), but also gives some performance. Should probably resubmit it again. The main issue was that the old single link patch is still not forward ported. https://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc.git/log/?h=lto-411-2 -Andi -- 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
