On Sat, Aug 03, 2013 at 04:47:29PM +0900, Mike Hommey wrote:
> On Sat, Aug 03, 2013 at 01:36:15PM +1000, Nicholas Nethercote wrote:
> (...)
> > Even worse, link times are through the roof.  I was thrilled when, two
> > years ago, I switched from ld to gold and linking time plummeted.  The
> > first link after rebooting was always slow, but I could link libxul
> > back then in about 9 seconds.  I haven't measured recently but I'm
> > certain it's now *much* higher.  Even the JS shell, which used to take
> > hardly any time to link, now takes 10s or more;  enough that I often
> > switch to doing something else while waiting.
> 
> The JS engine, having grown to be a lot of C++ instead of being mainly
> C, also saw its debugging info (DWARF) grow significantly. FWIW, the
> debug info .so for libmozjs.so at the time of Firefox 15 was 69MB on
> Linux64, it is 129MB in Firefox 22. More debug info means link time
> increase, and suggests build increase too (if debug info is bigger, it
> means either code is bigger, or code is more complex ; or both)
> 
> > If I could speed up any part of the builds, it would be linking.
> > Waiting a long time to test a one file change sucks.
> 
> If you're on linux, you can try --enable-debug-symbols=-gsplit-dwarf.

For those who would want to try it at home, note this doesn't work well
with ccache:
https://bugzilla.samba.org/show_bug.cgi?id=10005

Mike
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to