Correction: Looking at the code, it turns out that --print-code still does
what the name implies: it prints all code (optimized code, regexp code,
wasm code). It's just that there is no unoptimized code any more (which
arguably was the flag's primary use case in the past).
On Mon, Feb 12, 2018 at
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
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
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
Hi,
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
