Re: [v8-users] Issues Linking to v8 - Linux/g++ (6.4.388.40)

2018-02-12 Thread Jerry Sievert
After following up (I've been hitting my head against this for a week at least), and updating ubuntu to another version, I've managed to get it to link and run by forcing -lc++ against libc++-dev and libc++-helper thanks Ben, you can stand down :) I appreciate the response, though. On Monday,

Re: [v8-users] Issues Linking to v8 - Linux/g++ (6.4.388.40)

2018-02-12 Thread Jerry Sievert
also forgot to add that I'm using -std=c++11 on compile On Monday, February 12, 2018 at 12:57:33 PM UTC-8, Jerry Sievert wrote: > > Thanks Ben, > > That's what I had been thinking as well, and moved to clang++-5.0 with > llvm's libc++ as well. > > libv8 is being built via: > > tools/dev/v8gen.py

Re: [v8-users] Issues Linking to v8 - Linux/g++ (6.4.388.40)

2018-02-12 Thread Jerry Sievert
Thanks Ben, That's what I had been thinking as well, and moved to clang++-5.0 with llvm's libc++ as well. libv8 is being built via: tools/dev/v8gen.py x64.release -- is_component_build=false v8_static_library=true v8_use_snapshot=true v8_use_external_startup_data=false ninja -C out.gn/x64.rel

Re: [v8-users] Issues Linking to v8 - Linux/g++ (6.4.388.40)

2018-02-12 Thread Ben Noordhuis
On Mon, Feb 12, 2018 at 9:29 PM, Jerry Sievert wrote: > Hello, > > Apologies if this is the wrong place to post - I've also searched, and have > been unable to find an answer. > > I've been attempting to link to v8, with an environment that has worked fine > in the past with older versions of v8 (

[v8-users] Issues Linking to v8 - Linux/g++ (6.4.388.40)

2018-02-12 Thread Jerry Sievert
Hello, Apologies if this is the wrong place to post - I've also searched, and have been unable to find an answer. I've been attempting to link to v8, with an environment that has worked fine in the past with older versions of v8 (make native, as opposed to ninja). I've updated for any API cha

Re: [v8-users] --print-code does not work

2018-02-12 Thread 'Mathias Bynens' via v8-users
Tracking issue for the removal of --print-code: https://bugs.chromium.org/p/v8/issues/detail?id=7437 On Fri, Feb 9, 2018 at 11:22 PM, Jakob Kummerow wrote: > If --print-opt-code prints nothing, then probably your function isn't > getting optimized. Try calling it more often. > > --print-code is

Re: [v8-users] --print-code does not work

2018-02-12 Thread Istvan Tabanyi
Oh god, I put it in a for loop already, but turned out 9000 iterations was not enough, doh. Thanks for advice, all fine:) On Friday, 9 February 2018 23:23:01 UTC+1, Jakob Kummerow wrote: > > If --print-opt-code prints nothing, then probably your function isn't > getting optimized. Try calling i