Requirements to use flto

gcc ld binutils lto gold-linker
chew socks picture chew socks · Jul 29, 2015 · Viewed 17.7k times · Source

If I want to compile my project with -flto is it enough to have built gcc with --enable-gold or do I also need to build gold and replace ld with it? And do I need any other flags? Ie I'm doing this

gcc -flto one.c two.c

Answer

melpomene picture melpomene · Jul 29, 2015

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.

Related questions

How to set 2 byte wchar_t output?

The GCC uses a 4-byte wchar_t by default. I can set the option -fshort-wchar to get 2 bytes per wchar_t in the L"string constants". But when I set the compiler option to my source file I get the …

Read More
unable to compile: unrecognized relocation 0x2a in section text

I have received an error message when compiled "make" $ make g++ -fopenmp -o lang.test main.o -I../../../include/Lheader -I../../../include -L../../../lib/ -llmi -lblas -lboost_regex -lpthread -lleveldb /usr/bin/ld: ../../../lib//liblmi.a(LMInterface.o): unrecognized relocation (0…

Read More
Does the order of -l and -L options in the GNU linker matter?

The -l option tells the linker to search the libraries in the standard dirs. And with -L, we can specify our own library directories for searching. Question: Does the sequence of order matters for the -L option too, like it …

Read More