[v8-users] The v8 6.8 and 6.9 version does not get the libv8_snapshot.a library

I can get libv8_snapshot.a with the stable version of 6.5, but the later stable version such as 6.8, 6.9 does not have libv8_snapshot.a library after compiling, but I have to use libv8_snapshot.a library when embedding android, because only this is used. The library will not report an error.

Re: [v8-users] How do compile the code coverage for V8?

I first tried to build using Ubuntu 16.04 latest gcc version. (I don't remember the details, but I probably remember the version 6.0) However, when tested in the latest gcc based on the same args, the following linker error occurred: python "../../build/toolchain/gcc_solink_wrapper.py"

[v8-users] Re: trying to understand v8's opt/deopt strategy, is this behavior normal?

Not a V8 dev, but: - What's the offending code triggering the opt/deopt loop look like? That should help quite a bit in understanding what's going on. - Opt/deopt loops are engine bugs - it should never do that. V8 should figure out at some point whether to optimize or completely bail out.

Re: [v8-users] How do compile the code coverage for V8?

It seems like this warning ("class-memaccess") was introduces in gcc 8.0, which we do not test currently. Can you try compiling with an older gcc version? On Tue, Sep 4, 2018 at 4:14 AM wrote: > Hello > I create gn files with args. > > gn args test/ --args='target_cpu="x64"