Re: [JS-internals] [Fixed] Do Not Land: AWFY is not responding.

2013-10-15 Thread Nicolas B. Pierron
On 10/15/2013 01:11 PM, Jason Orendorff wrote: On 10/15/13 12:40 PM, Nicolas B. Pierron wrote: AWFY is our last barrier to prevent regressions. Currently, all slaves are down! Until AWFY is fixed, I suggest that we do not land anything to the JS Engine unless we provide benchmark results for s

Re: [JS-internals] Do Not Land: AWFY is not responding.

2013-10-15 Thread Jason Orendorff
On 10/15/13 12:40 PM, Nicolas B. Pierron wrote: > AWFY is our last barrier to prevent regressions. Currently, all > slaves are down! > > Until AWFY is fixed, I suggest that we do not land anything to the JS > Engine unless we provide benchmark results for sunspider and kraken. > V8 still runs on

[JS-internals] Do Not Land: AWFY is not responding.

2013-10-15 Thread Nicolas B. Pierron
Hi, AWFY is our last barrier to prevent regressions. Currently, all slaves are down! Until AWFY is fixed, I suggest that we do not land anything to the JS Engine unless we provide benchmark results for sunspider and kraken. V8 still runs on tbpl[1]. [1] http://graphs.mozilla.org/graph.h

Re: [JS-internals] Performance impact of Debugger

2013-10-15 Thread Jim Blandy
On 10/14/2013 10:18 AM, Jason Orendorff wrote: On 10/14/13 12:03 PM, Jim Blandy wrote: [...]there's probably no need to separate bytecode instructions that have no visible side effects from their successors. Filed bug 926528, " JSD2: Reduce the number of positions where a breakpoint can be plac