The ARM64 backend could convert Smi to Operand by assigning tagged Smi to
immediate filed in Operand class, as below code snippet. Then the immediate
field is tagged Smi value, would it cause problem when encoding this
operand?
// src\arm64\assember-arm64-inl.h
*template*<>
*struct*
The ARM64 backend could convert Smi to Operand by assigning tagged Smi to
immediate filed in Operand class, as below code snippet. Then the immediate
field is tagged Smi value, would it cause problem when encoding this
operand?
// src\arm64\assember-arm64-inl.h
template<>
struct
On Thu, Apr 19, 2018 at 6:59 PM, Andrew Walker wrote:
> I'm attempting to Dockerize an application that uses a particular set of
> golang bindings to V8, and I'm having a bear of a time building v8. I can't
> seem to even get past `fetch v8`. Just to see where it's going
Did you see https://github.com/v8/v8/wiki/Building-from-Source? To build
all targets, just use:
$ ninja -C out.gn/golib/
On Fri, Apr 20, 2018 at 7:25 AM, Andrew Walker wrote:
> I am attempting to build v8 in a wheezy VM for a binding that links
> against
>
>- libv8
>
Have a look at [0], which describes the memory layout of code objects. The
RelocInfo is currently a separate object and Code objects store a pointer
to it.
[0]
https://cs.chromium.org/chromium/src/v8/src/objects/code.h?l=369=ff6b34b468c1eae8589b278923f87e2f573bc248
On Thu, Apr 19, 2018 at 11:57