On Sat, Jul 14, 2012 at 5:00 PM, Toon Moene <t...@moene.org> wrote: > I have been using the option -flto-partition=none recently (with Debian > testing's gcc-4.7.1-2), but I'm not convinced - based on the documentation - > that I am using it correctly. > > I have: > > for C source code: > > CCFLAGS := -g -Ofast -flto -march=native -mtune=native > > for Fortran source code: > > FCFLAGS := -g -Ofast -flto -fprotect-parens -fbacktrace -march=native > -mtune=native -I$(HOME)/netcdf/include > > and for the final link stage: > > LDFLAGS := -g -Ofast -flto -flto-partition=none -fuse-linker-plugin > -fprotect-parens -fbacktrace -march=native -mtune=native > > 1. Is it correct to assume that -flto-partition=alg is only necessary during > the final link stage ? If so, shouldn't that be made clear in the > documentation ?
Yes, -flto-partition is only relevant at link stage > 2. What is the relation with -flto=n; doesn't no-partitioning imply -flto=1 > ? If so, shouldn't that be made clear in the documentation ? -flto=n is just on how to parallelize the compile done at link stage. If you specify -flto-partition=none there is nothing to parallelize. For the default -flto-partition setting we generate up to 24 ltrans files (or was 42?) which are then built by make -jN (for -flto=N) or by means of picking up make flags (for -flto=jobserver). Richard. > -- > Toon Moene - e-mail: t...@moene.org - phone: +31 346 214290 > Saturnushof 14, 3738 XG Maartensdijk, The Netherlands > At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/ > Progress of GNU Fortran: http://gcc.gnu.org/wiki/GFortran#news
