If you are going to go through all this trouble to optimize for the
isolate, you
probably should make these inlined for the fast case of looking up a 31-bit
signed integer. If you inline that case and then fall back to api.cc only
when
you need to allocate a heap number. If you do that, I suspect that it will
as
fast as the integer cache, unless webkit often caches integers where the
than
don't fit in the 31-bit signed range.
https://codereview.chromium.org/11212004/
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
