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 it more often.
> --print-code is "technically correct" in the sense that it prints all of
> the unoptimized machine code that V8 doesn't generate any more ;-)
> (We should remove the flag.)
> On Fri, Feb 9, 2018 at 1:18 AM Istvan Tabanyi <st...@powerednow.com
>> I compiled v8 from sources successfully, but
>> --print-code/--print-opt-code gives me no output at all.
>> --print-bytecode works fine, --print-all-code prints something, but the
>> actual code is definitely not in the output(Created a simple function with
>> unique name, called in a loop, grepped for it and nothing)
>> Tried release and debug builds, also with custom options like this:
>> gn gen out.gn/x64.debug --args='is_debug=true target_cpu="x64"
>> v8_target_cpu="x64" v8_enable_disassembler=true'
>> I tried to look for tutorials on this topic, but most of it really
>> outdated and using make/gyp.
>> Can someone give me some tips about this? And sorry if this is not the
>> right place to ask questions like this.
>> v8-users mailing list
>> 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
>> For more options, visit https://groups.google.com/d/optout.
v8-users mailing list
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.