http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59469
--- Comment #6 from Jan Hubicka <hubicka at gcc dot gnu.org> --- With -fno-fat-lto-objects we are also faster on SPEC build time and I think it should be the case in general. We produce considerably less code and most of time is spent in the backend. For super large projects with parallel makefiles the time spent in serial WPA may overweight the benefits, but for GCC and firefox I believe the only problem is that it builds multiple binaries from same static libraries. Here we end up optimizing the static libraries many times, while in traditional build we optimize just once. Let me see if I can reproduce the weak symbol. In these cases my life would be a lot easier if you attached the resolution file and told me the unmangled name of the symbol. But thanks a lot for the analysis and LTO testing! It is badly needed.
