Re: [JS-internals] Getting the allocation point of every object

2014-03-17 Thread Nicholas Nethercote
On Wed, Feb 26, 2014 at 7:29 PM, Till Schneidereit wrote: >> >> >> I have this working now. In the output I see quite a few lines of the >> >> "??? (1)" form, i.e. the NonBuiltinScriptFrameIter has zero elements. >> >> I'm not sure what this means... allocations triggered from within C++ >> >> cod

Re: [JS-internals] Getting the allocation point of every object

2014-02-27 Thread Jason Orendorff
On 2/27/14, 5:02 AM, Brendan Eich wrote: > Fitzgerald, Nick wrote: >> Or in self hosted code, right? Maybe the iterator { value, done } >> objects? > > Are we optimizing away { value, done } objects that can't escape (from > iterators run afresh by for-of loops)? No, except in the relatively rare,

Re: [JS-internals] Getting the allocation point of every object

2014-02-27 Thread Nicolas B. Pierron
On 02/27/2014 03:02 AM, Brendan Eich wrote: Fitzgerald, Nick wrote: Or in self hosted code, right? Maybe the iterator { value, done } objects? Are we optimizing away { value, done } objects that can't escape (from iterators run afresh by for-of loops)? If not, is there a bug on file to so opti

Re: [JS-internals] Getting the allocation point of every object

2014-02-27 Thread Brendan Eich
Fitzgerald, Nick wrote: Or in self hosted code, right? Maybe the iterator { value, done } objects? Are we optimizing away { value, done } objects that can't escape (from iterators run afresh by for-of loops)? If not, is there a bug on file to so optimize? If not, please file and cite here. Th

Re: [JS-internals] Getting the allocation point of every object

2014-02-26 Thread Till Schneidereit
On Thu, Feb 27, 2014 at 4:09 PM, Nicholas Nethercote wrote: > >> I have this working now. In the output I see quite a few lines of the > >> "??? (1)" form, i.e. the NonBuiltinScriptFrameIter has zero elements. > >> I'm not sure what this means... allocations triggered from within C++ > >> code ra

Re: [JS-internals] Getting the allocation point of every object

2014-02-26 Thread Nicholas Nethercote
>> I have this working now. In the output I see quite a few lines of the >> "??? (1)" form, i.e. the NonBuiltinScriptFrameIter has zero elements. >> I'm not sure what this means... allocations triggered from within C++ >> code rather than JS code? > Or in self hosted code, right? Maybe the iterator

Re: [JS-internals] Getting the allocation point of every object

2014-02-26 Thread Fitzgerald, Nick
On 2/26/14 5:20 PM, Nicholas Nethercote wrote: > I have this working now. In the output I see quite a few lines of the > "??? (1)" form, i.e. the NonBuiltinScriptFrameIter has zero elements. > I'm not sure what this means... allocations triggered from within C++ > code rather than JS code? Or in se

Re: [JS-internals] Getting the allocation point of every object

2014-02-26 Thread Nicholas Nethercote
On Wed, Feb 26, 2014 at 2:46 PM, Nicholas Nethercote wrote: > On Wed, Feb 26, 2014 at 2:29 PM, Nicholas Nethercote >> >> Suggestions on how to do this properly would be appreciated. The >> object metadata stuff is probably a better way to proceed here... > > billm pointed me to > http://mxr.mozil

Re: [JS-internals] Getting the allocation point of every object

2014-02-26 Thread Nicholas Nethercote
On Wed, Feb 26, 2014 at 2:29 PM, Nicholas Nethercote > > Suggestions on how to do this properly would be appreciated. The > object metadata stuff is probably a better way to proceed here... billm pointed me to http://mxr.mozilla.org/mozilla-central/source/js/src/builtin/TestingFunctions.cpp#1066

[JS-internals] Getting the allocation point of every object

2014-02-26 Thread Nicholas Nethercote
Hi, I'm doing some profiling of pdf.js, and I would like to get the allocation point for every object, either when it's allocated, and/or when the JS memory reporter runs. This is for some ad hoc profiling -- I just want to dump the info to stderr so I can post-process it -- so it doesn't need to