[Buildroot] [PATCH v2 1/1] toolchain: add link-time-optimization support
thomas.petazzoni at free-electrons.com
Sat Mar 7 14:28:52 UTC 2015
Dear Peter Kümmel,
On Fri, 6 Mar 2015 13:34:06 +0100, Peter Kümmel wrote:
> Add a new option BR2_GCC_ENABLE_LTO that builds gcc and binutils with LTO support.
> Individual packages still have to enable LTO explicitly by passing '-flto' to
> GCC, which passes it on to the linker. This option does not add that flag
> globally. Some packages detect if the compiler supports LTO and enable the flag
> if it does.
> To support LTO, ar and ranlib must be called with an argument which triggers the
> usage of the LTO plugin. Since GCC doesn't call these tools itself, it instead
> provides wrappers for ar and ranlib that pass the LTO arguments. This way
> existing Makefiles don't need to be changed for LTO support. However, these
> wrappers are called <tuple>-gcc-ar which matches the pattern to link to the
> buildroot wrapper in the external toolchain logic. So the external toolchain
> logic is updated to provide the correct symlink.
> Signed-off-by: Peter Kümmel <syntheticpp at gmx.net>
Thanks, applied, after doing a few changes:
- Add a separate BR2_BINUTILS_ENABLE_LTO option to enable LTO
support in binutils. This is a blind option, selected by
BR2_GCC_ENABLE_LTO. It just avoids having binutils.mk poke
directly into gcc Config.in options.
- Remove the check on the AVR32 special gcc version, which we don't
- Adapt the help text of the LTO Config.in option to no longer
mention "Since version 4.5", since we only support gcc >= 4.5 in
- Fix typo in toolchain-external.mk comment.]
I did a test build, and I could see the difference in the generated
code between a -flto build a non -flto build of a stupid test
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
More information about the buildroot