As indicated in the announcement I just sent, this is just simple byte sizes
right now, but it should be convenient to add more measurements now that we
have a step in the buildbot for it.
I'll take a look at Codesighs to see what we might be able to incorporate.
Dean also had a link to a Windows-specific utility that dumped useful size
info.
--SK
Sounds interesting... how did you implement size tracking? Just looking at
> the size of chrome.dll or the total zip or ...?
> Mozilla has a very nice tool that shows the delta for each symbol in each
> binary. It is very helpful for understand where code size changes come
> from.
>
> Some info:
> https://wiki.mozilla.org/Codesighs
>
> -Darin
>
>
> On Thu, Apr 16, 2009 at 4:16 PM, Steven Knight <[email protected]> wrote:
>
>> Heads up:
>>
>> I'd like to take the buildbot off line tonight, ~22:00 PDT, to add size
>> tracking to the release builders. It should not be down long. Let me know
>> if that would interfere with any plans you have.
>>
>> Thanks,
>>
>> --SK
>>
>>
>> >>
>>
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: [email protected]
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
