9 Feb 2007 19:35
Top level intermodule profiledbootstrap, for people with too much free time.
Robert Connolly <robert <at> linuxfromscratch.org>
2007-02-09 18:35:29 GMT
2007-02-09 18:35:29 GMT
I wrote this a few weeks ago... # The following is a study of possible ways to optimize the GNU toolchain. # # First of all, I made the assumption that using the Top Level Makefile # system, included with the recent GCC and Binutils versions, has a greater # potential for optimizing the applications than building them each # separately. I also did not study non-bootstrapped builds because a # non-bootstrapped toolchain has no reason to perform better than a # bootstrapped toolchain. # I performed this study with all the tricks I know of to optimize the # toolchain, including intermodule builds, profiled builds, and GNU hash # style. # The top level makefile system also adds the potential of profiling a pile of # other packages, like flex and bison and gettext and bash and findutils and # much more. But I have yet to get that to work for me. # The --enable-intermodule option will make GCC use the -combine option # to compile all sources in the same command line. The idea is that the # compiler can optimize all the sources together and make better judgments. # This option should also take better advantage of the -O3 option. The only # other package I know of that uses -combine (and also uses -fwhole-program) # is Busybox, because it not only increases performance but also decreases # program size (about 1%). # My system is a Pentium 4 prescott, 3GHZ, with 1024MB of physical memory. # Running kernel 2.6.19.2, and Glibc-2.5. This toolchain version's are the # same versions on the chrooted host system (chapter 6 LFS). I have a 1024MB(Continue reading)
Or is it the actual
source tarballs you were after? In which case, I can't help I'm afraid.
Matt.
RSS Feed