Did you notice the bit in the GCC 4.9 release notes about LTO with Firefox?
https://gcc.gnu.org/gcc-4.9/changes.html With LTO enabled, they remarked: "Memory usage building Firefox with debug enabled was reduced from 15GB to 3.5GB; link time from 1700 seconds to 350 seconds." ... Does this mean you can now enable LTO, if you haven't already? (I guess you turned it off so far because of the mildly ridiculous compute requirements). That might yield substantial binary size reduction, which would be nice... On 03/06/15 16:21, James Willcox wrote: > Later today I am planning to push some changes that will make the > builders use NDK r10e and GCC 4.9. We needed to upgrade the NDK to work > around a PIE linking issue on x86, and the latest NDK only has GCC 4.8 > and 4.9. I've been using 4.9 locally for a while now, so I don't expect > too many issues, but developers should consider upgrading their local > copies too. > > One nice thing about GCC 4.9 is that it supports colorized errors and > warnings, which can really help identify problems during the build. > You'll be able to enable this with the following bits in your mozconfig: > > export CFLAGS="-fdiagnostics-color" > export CPPFLAGS="-fdiagnostics-color" > export CXXFLAGS="-fdiagnostics-color" > export LDFLAGS="-fdiagnostics-color" > > We should probably add a --enable-color-diagnostics configure option to > do this for you. > > Thanks, > James > > > _______________________________________________ > mobile-firefox-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/mobile-firefox-dev > _______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev

