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
(2014/09/22 0:03), Si Robertson wrote:
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?
Yes, Smi's are 32-bits in x64.
In other
Dear all:
I'm sorry, it isn't a v8 specified topic, but I really need your help.
Now I want to use a static library lib*.a in Chromium project, but how to
link it .
For example, I will use it normally as follow:
gcc test.c -L(path) -l*
But in chromium project how to add it ？
Thank you
You should ask on the Chromium (or very maybe the V8-dev) lists.
It will likely involve understanding how to write GYP files. Which is kind
of a mess, especially in Chrome and V8.
On Sunday, September 21, 2014 8:52:58 PM UTC-8, Liu Xiao wrote:
Dear all:
I'm sorry, it isn't a v8 specified
