On Sat, Sep 24, 2016 at 2:40 AM, Jane Chen <[email protected]> wrote: > Thanks, Ben! > > I added that flag to my v8 init code. Now I get: > > 12 xdmp::JSEngine::evalBuiltin() > /space/projects/head/xdmp/src/JSEngine.cpp:11794 0x000000000391466e > 11 xdmp::JSEngine::evalBuiltin() > /space/projects/head/xdmp/src/JSEngine.cpp:11766 0x00000000039141ec > 10 v8::internal::FunctionCallbackArguments::Call() > /space/projects/v8-git/v8/src/api-arguments.cc:19 0x00007ffff549cef9 > 9 v8::internal::(anonymous namespace)::HandleApiCallHelper<false>() > /space/projects/v8-git/v8/src/builtins.cc:5311 0x00007ffff5521150 > 8 v8::internal::Builtin_Impl_HandleApiCall() > /space/projects/v8-git/v8/src/builtins.cc:5341 0x00007ffff5569d92 > 7 v8::internal::Builtin_HandleApiCall() > /space/projects/v8-git/v8/src/builtins.cc:5329 0x00007ffff5524c1d > 6 <symbol is not available> 0x0000332193c06147 > 5 <symbol is not available> 0x0000332193c06081 > 4 <symbol is not available> 0x00007ffad924d2a0 > 3 <symbol is not available> 0x0000000300000000 > 2 <symbol is not available> 0x00007ffad924d308 > 1 LazyCompile:~isPrime :1() 0x0000332193c6b884 > > I suppose that's as good as it gets, right? Any performance penalties to > leave it on always?
I suppose so; does --gdb_jit_full make a difference? As to performance: 1. --gdb_jit implies --nocompact_code_space so the code space (where generated machine code is stored) may get fragmented over time. I have never observed that to be a problem in practice, though, even in long-running programs. 2. There is some bookkeeping involved but it's not huge. Your application may run a few percent slower, depending on what it does. -- -- v8-users mailing list [email protected] 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
