According to https://gcc.gnu.org/wiki/LinkTimeOptimization#Requirements,
Despite the "link time" name, LTO does not need to use any special linker features. The basic mechanism needed is the detection of GIMPLE sections inside object files. This is currently implemented in collect2
. Therefore, LTO will work on any linker already supported by GCC.
Furthermore, the GCC documentation for -fuse-linker-plugin
says:
This option is enabled by default when LTO support in GCC is enabled and GCC was configured for use with a linker supporting plugins (GNU ld 2.21 or newer or gold).
So you don't need gold
at all, even if you want to use the special "linker plugin" feature to pick up optimization information from object files in library archives.
There are usage examples in the -flto
documentation. Either
gcc -o myprog -flto -O2 foo.c bar.c
or
gcc -c -O2 -flto foo.c
gcc -c -O2 -flto bar.c
gcc -o myprog -flto -O2 foo.o bar.o
will work.
As of GCC 4.9, you don't even need -flto
for linking:
The only important thing to keep in mind is that to enable link-time optimizations you need to use the GCC driver to perform the link-step. GCC then automatically performs link-time optimization if any of the objects involved were compiled with the -flto
.
And as of GCC 5:
Contrary to earlier GCC releases, the optimization and target options passed on the link command line are ignored.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…