On Tue, Dec 03, 2013 at 01:30:39PM -0800, Jed Davis wrote: > On Tue, Dec 03, 2013 at 11:47:48AM -0800, L. David Baron wrote: > > On Tuesday 2013-12-03 10:18 -0800, Brian Smith wrote: > > > Also, I would be very interested in seeing "size of libxul.so" for > > > fully-optimized (including PGO, where we normally do PGO) builds. Do > > > unified builds help or hurt libxul size for release builds? Do unified > > > builds help or hurt performance in release builds? > > > > I'd certainly hope that nearly all of the difference in size of > > libxul.so is debugging info that wouldn't be present in a non-debug > > build. But it's worth testing, because if that's not the case, > > there are some serious improvements that could be made in the C/C++ > > toolchain... > > At the risk of stating the obvious, localizing the size change should > be a simple matter of `readelf -WS`. If we're seeing actual change > in .text size by way of per-directory sort-of-LTO, then that would be > interesting (and could be localized further with the symbol table).
Or using size, which I did, but didn't paste and I don't have the data anymore. IIRC, size tends to be smaller with higher number of unified sources, but not by a big margin. Mike _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
