It optimizes integers for 32 bits because there is little reason to optimize integers for anything else when the ECMAScript specification itself makes no mention of 64-bit integers, only 32-bit ones beyond smaller sizes for typed arrays.
On Sunday, September 21, 2014 12:03:18 PM UTC-4, Si Robertson wrote: > > Hi guys, > > When working with integers and V8 I have always been aware of keeping > integer values within a 31-bit range for performance reasons. Does the > introduction of Chrome 64-bit affect the bit-length of integer values? In > other words, can V8 in Chrome 64-bit handle 63-bit integer values > performantly or does it still prefer 31-bit integer values? > > Thanks. > > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
