Hi, > how do i see why the method is deopted? for example here:
If you --trace-deopt with --code-comments then in most cases you will get LIR instruction that deopted in the output (though it is not always correct). The only reliable way to figure what caused deopt is run with --print-opt-code and go read assembly around deopt point. > does that mean i should replace the for in with a for loop that iterates > over Object.keys? Yes. -- Vyacheslav Egorov On Thu, Oct 11, 2012 at 11:48 AM, Christoph Sturm <m...@christophsturm.com> wrote: > I'm trying to optimize my node app with --trace-deopt > > how do i see why the method is deopted? for example here: > > **** DEOPT: Wlbl.Checker.checkUrl at bailout #24, address 0x0, frame size 88 > [deoptimizing: begin 0x25d8e5e85e71 Wlbl.Checker.checkUrl @24] > translating Wlbl.Checker.checkUrl => node=260, height=40 > > also when i log optimizer bailouts, i see this: > Bailout in HGraphBuilder: @"exports.paramsToString": ForInStatement is not > fast case > > does that mean i should replace the for in with a for loop that iterates > over Object.keys? > > thanks > chris > > -- > v8-users mailing list > v8-users@googlegroups.com > http://groups.google.com/group/v8-users -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users
