On Tue, Jan 28, 2014 at 4:29 AM, Till Schneidereit < [email protected]> wrote:
> On Tue, Jan 28, 2014 at 10:11 AM, Tom Schuster <[email protected]> wrote: > > > * Dev Tools improvements > > IIRC we have been discussing this for the last two work weeks, but the > > actual result of JS specific features seem to be rather low. I know we > > landed some stuff like setMetadata, but I am not sure if it's even used? > > Recently I saw some things about Memory maps that seem very exciting. > > > > There's lots of work going on regarding better devtools support. Ranging > from getting a much better story for memory reporting over better support > for dynamically-created (i.e., evaled) code in the debugger to debugging > workers. Plus, reducing the overhead of instrumentation such as SPS. > > Having said that, what would be great is if we could somehow make use of > the fact that the devtools team is having a work week shortly before ours. > Maybe someone could go there and collect information that can the inform > our planning? > I was working on teaching the Debugger about the JITs. Allowing the Debugger to be turned on with live scripts on the stack is the first step, then I plan to add hooks such as onDeoptimization and the like to further performance debugging and JIT transparency in general. I have a stack of patches on bug 716647 already but had to pause my efforts to go back to working on PJS. With Lars starting, I should have more cycles to work on the devtools patches. FWIW, I am also going to the devtools work week in PDX in Feb. -- shu _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
