On Fri, Feb 21, 2014 at 7:15 AM, Gabriele Svelto wrote:
> On 20/02/2014 18:57, arpad.bor...@googlemail.com wrote:
> > And yes, allocation counts would be awesome. Any idea how to get to
> those? Or even better: number of average live objects, since short lived
> allocations do not matter that much
On 20/02/2014 18:57, arpad.bor...@googlemail.com wrote:
> And yes, allocation counts would be awesome. Any idea how to get to those? Or
> even better: number of average live objects, since short lived allocations do
> not matter that much.
Just thinking out loud: some memory reporters should alr
> What do the fractions mean?
Those are from bitfields. clang also reports those as "padding struct X with Y
*bits*..."
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Arpad Borsos wrote:
I updated my methodology for finding wasted bytes in
https://bugzilla.mozilla.org/show_bug.cgi?id=492185#c35.
It just sums up all the stuff that clangs `-Wpadded` warnings gives us.
njn suggested I post the complete list, so here goes. Feedback welcome.
What do the fracti
> Also, a question. These are 64-bit numbers, right?
Yes.
Also please take these numbers with a grain of salt. I simply sum up what clang
gives as warnings. For example, I have no idea how it handles unions.
And yes, allocation counts would be awesome. Any idea how to get to those? Or
even be
On 2/20/14 5:27 AM, Arpad Borsos wrote:
njn suggested I post the complete list, so here goes. Feedback welcome.
It'd be pretty awesome to get some idea of the number-of-objects
distribution for these objects, so we have a metric of how much memory
we'd save. Saving 58 bytes in the singleton
6 matches
Mail list logo
