Updates:
Status: Fixed
Comment #4 on issue 1758 by [email protected]: Performance penalty
when using integers > 30bit
http://code.google.com/p/v8/issues/detail?id=1758
I just reran the test code above on Chrome 18.0.976.0 (32-bit Linux) and
there is no significant difference between using 32bit or 30bit. So I'm
marking this as resolved.
I pretty sure that this is because of the improvements in inlining that
allows the optimized code to handle 32bit integers without going slow-case.
Basically, as long as the values stay in local variables, V8 is very
efficient on 32-bit integers. A slowdown may happen if 32bit values are
written into objects or arrays. For this case Int32Array is recommended for
maximum performance.
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
