Re: Analyze C++/compiler usage and code stats easily

2013-11-29 Thread Gregory Szorc
On 11/29/13, 4:00 AM, Ehsan Akhgari wrote: On 11/25/2013, 7:41 PM, Gregory Szorc wrote: The repo was hiding that old changeset because it has been obsoleted (Mercurial changeset evolution magic). I updated the server config to expose hidden changesets, so the link works again. However, the chan

Re: Analyze C++/compiler usage and code stats easily

2013-11-28 Thread Ehsan Akhgari
On 11/25/2013, 7:41 PM, Gregory Szorc wrote: The repo was hiding that old changeset because it has been obsoleted (Mercurial changeset evolution magic). I updated the server config to expose hidden changesets, so the link works again. However, the changeset has been obsoleted, so you'll want to

Re: Analyze C++/compiler usage and code stats easily

2013-11-26 Thread Neil
Gregory Szorc wrote: The best way to fetch it is to pull the bookmark tracking it: $ hg pull -B gps/build/measure-compiler http://hg.gregoryszorc.com/gecko-collab Or, look for that bookmark at http://hg.gregoryszorc.com/gecko-collab/bookmarks and track down the changeset. Note that for

Re: Analyze C++/compiler usage and code stats easily

2013-11-25 Thread Gregory Szorc
The repo was hiding that old changeset because it has been obsoleted (Mercurial changeset evolution magic). I updated the server config to expose hidden changesets, so the link works again. However, the changeset has been obsoleted, so you'll want to fetch the newest one. The best way to fet

Re: Analyze C++/compiler usage and code stats easily

2013-11-25 Thread Ehsan Akhgari
This patch doesn't seem to exist any more. Do you have another copy of it lying somewhere? Thanks! -- Ehsan On Fri, Nov 15, 2013 at 12:43 AM, Gregory Szorc wrote: > C++ developers, > > Over 90% of the CPU time required to build the tree is spent compiling or > link

Re: Analyze C++/compiler usage and code stats easily

2013-11-16 Thread Gregory Szorc
I updated the patch to be a little bit more robust. New version at http://hg.gregoryszorc.com/gecko-collab/rev/6af8ba812e82 I also put together some lists of compiler CPU time per directory: https://gps.pastebin.mozilla.org/3613688 https://gps.pastebin.mozilla.org/3620053 In terms of percent:

Re: Analyze C++/compiler usage and code stats easily

2013-11-16 Thread Terrence Cole
On 11/15/2013 05:37 PM, Gregory Szorc wrote: > On 11/15/13, 12:26 PM, Terrence Cole wrote: >> The problem this mess is solving, at least in the GC, is that gecko >> needs to be able to inline barriers, UnmarkGray, and misc other stuff. >> Whenever we accidentally out-of-line anything in these paths

Re: Analyze C++/compiler usage and code stats easily

2013-11-15 Thread Gregory Szorc
On 11/15/13, 12:26 PM, Terrence Cole wrote: The problem this mess is solving, at least in the GC, is that gecko needs to be able to inline barriers, UnmarkGray, and misc other stuff. Whenever we accidentally out-of-line anything in these paths we see a tremendous slowdown on dromaeo_dom and droma

Re: Analyze C++/compiler usage and code stats easily

2013-11-15 Thread Terrence Cole
On 11/15/2013 06:51 AM, Jason Orendorff wrote: > On 11/14/13 11:43 PM, Gregory Szorc wrote: >> * Why does lots of js/'s source code gravitate towards the "bad" >> extreme for most of the metrics (code size, compiler time, >> preprocessor size)? > > We use templates very heavily and we inline like

Re: Analyze C++/compiler usage and code stats easily

2013-11-15 Thread Jason Orendorff
On 11/14/13 11:43 PM, Gregory Szorc wrote: > * Why does lots of js/'s source code gravitate towards the "bad" > extreme for most of the metrics (code size, compiler time, > preprocessor size)? We use templates very heavily and we inline like mad. Templates make C++ compilers go slowly. The GC sma

Re: Analyze C++/compiler usage and code stats easily

2013-11-15 Thread Boris Zbarsky
On 11/15/13 12:43 AM, Gregory Szorc wrote: * The mean ratio of .o size to lines from preprocessor is 16.35 bytes/line. Why do 38/4916 (0.8%) files have a ratio over 100? Why are a lot of these in js/ and gfx? * What's in the 150 files that have 100k+ lines after preprocessing that makes them so

Re: Analyze C++/compiler usage and code stats easily

2013-11-14 Thread Trevor Saunders
On Thu, Nov 14, 2013 at 09:43:01PM -0800, Gregory Szorc wrote: > C++ developers, > > Over 90% of the CPU time required to build the tree is spent > compiling or linking C/C++. So, anything we can do to make that > faster will make the overall build faster. > > I put together a quick patch [1] to

Analyze C++/compiler usage and code stats easily

2013-11-14 Thread Gregory Szorc
C++ developers, Over 90% of the CPU time required to build the tree is spent compiling or linking C/C++. So, anything we can do to make that faster will make the overall build faster. I put together a quick patch [1] to make it rather simple to extract compiler resource usage and very basic