Updates:
Status: WorkingAsIntended
Comment #1 on issue 1676 by [email protected]: NewGC: EarleyBoyer gets
stuck on debug build
http://code.google.com/p/v8/issues/detail?id=1676
We are getting very unfortunate type feedback and optimize
one_way_unify1_nboyer in such a way that it deopts on the second recursive
invocation of itself.
Because we do not support removal of the optimized code for recursive
invocations we never reoptimize this function and experience constant
deopts (the function is pretty hot).
On bleeding edge we sometimes (1 of 10 runs) optimize this function with
bad type feedback as well and performance also suffers.
http://codereview.chromium.org/7890028 is intended to solve the issue on
bleeding edge by forcing lazy deopt and replace optimized code on the
function with non-optimized one.
It also seems that GcSafeFindCodeForPc performs worse (at least in debug
build I am getting more ticks in this function) on GC branch compared to
bleeding edge. I'll file a separate issue for this.
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
