http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48913
--- Comment #2 from Sven C. Dack <sdack at gmx dot de> 2011-05-06 12:35:57 UTC --- I understand that it can use a lot of memory, but does LTO not partition the work load and thus keep the memory consumption under control? Whatever the default behaviour of LTO here is, it should not just run off and consume >8GB of RAM. Here is the information you have requested: $ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/home/sven/gcc/libexec/gcc/x86_64-unknown-linux-gnu/4.6.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: /var/tmp/build-pkg-31073/gcc-4.6.0/configure --prefix=/home/sven/gcc --with-gnu-as --with-gnu-ld --with-gmp=/home/sven/gcc --with-mpfr=/home/sven/gcc --with-mpc=/home/sven/gcc --with-ppl=/home/sven/gcc --with-cloog=/home/sven/gcc --enable-cloog-backend=isl --enable-stage1-languages=c,lto --enable-languages=c,c++,lto --with-build-config=bootstrap-lto Thread model: posix gcc version 4.6.0 (GCC) $ ld --version GNU ld (GNU Binutils) 2.21 Copyright 2010 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License version 3 or (at your option) a later version. This program has absolutely no warranty. The process that consumes all the memory is called "lto1".
