The reason I suggested a counter is an intuition about aging of code. If a
function has been executed zero times, then it should be thrown away
immediately
during GC. If it has been executed only once, it probably was global
initialization code and probably should be thrown away quickly, too. If a
function has been executed 2 or more times, it probably is something that is
worth keeping around since it might be executed again.
Is there any reason to not have this optimization always on, not just for
low-memory devices? If there is no regression, it seems like I would prefer
having a unified policy, it reduces the testing matrix and makes tracking
down
problems easier.
https://codereview.chromium.org/23480031/
--
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
