News for hackers. Stuff that matters.
Re:Chrome Binary Size by mtigas on Monday September 20, 2010 @08:59PM (#1711064)
I do have to point out that this visualization represents the binary executable size of Chrome, not the source tree. (According to another comment, it's generated with http://github.com/martine/bloat .)

Noticed a lot of folks linking to directory treesize visualizations.

This — breaking down a compiled binary to show the size of it’s constituent components — is a ton more interesting to me.

Re:Chrome Binary Size by Lerc on Monday September 20, 2010 @09:59PM (#1711191)
...and yet it includes header files. curious.

Looking at what's there, it looks like it can compile and run C (in nativeclient?).

Re:Chrome Binary Size by caf on Tuesday September 21, 2010 @01:13AM (#1711555)
It's possible to define symbols in header files (for example, inline functions).
Re:Chrome Binary Size by _delirium on Tuesday September 21, 2010 @01:42AM (#1711602)
I thought the way the C preprocessor worked, those ended up getting literally copy and pasted into the .c file that #include'd them, and should be indistinguishable from the case where you wrote them directly in the .c file? Or does gcc keep track of where #include'd files came from, and write that info into the binary?
Re:Chrome Binary Size by parbo on Tuesday September 21, 2010 @03:06AM (#1711782)
Yes, otherwise you'd never find syntax errors in the header files.
Re:Chrome Binary Size by scott_s on Tuesday September 21, 2010 @05:42PM (#1714207)
But that's during the compilation phase - this is the compiled binary. Binaries that are compiled with debugging information turned on will include this information for a similar reason: so that when you're debugging a program, or when it breaks, you can map that to places in your source file.
Re:Chrome Binary Size by caf on Wednesday September 22, 2010 @12:11AM (#1715143)
Right - and `nm` uses the debugging information to identify the file:line where each symbol was defined. The original scripts used to generate the treemap use `nm`.
Re:Chrome Binary Size by illumen on Tuesday September 21, 2010 @04:14AM (#1711877)
yes, and no. Whole program optimization kinda changes that. So do precompiled headers etc. Also chrome is C++.
Re:Chrome Binary Size by mfukar on Tuesday September 21, 2010 @05:14AM (#1711959)
Could be precompiled headers, inline functions, etc.