Hi everybody,
I'm trying to fully understand how Inline Cache misses and hits work on v8,
but I'm having trouble to understand the outputs of the --trace_ic,
--trace_opt and --trace_deopt flags. I'm a newbie in this area, but I've
used the searcher and I haven't found anything. I found one perso
On Mon, Sep 21, 2015 at 4:53 PM, Ignacio Queralt
wrote:
> [snip]
>
> My questions would be:
> 1) Where are the transitions between Uninitialized, and Monomorphic of the
> newadd function, for instance? I read that there are some Uninitialized ->
> Smi, but I can't see the relation in the output t
Thank you for your answer!
The runtime profiler is the one that decides if a function is hot, right?
I wanted to have a general understanding of how the IC works. How the
profiler runs, detects hot functions, or small functions, to optimize, and
tries to optimize them.
Basically, the Full compil
As I said before, the runtime profiler has nothing to do with ICs, neither
does optimized code. (Also, there isn't "the IC", there are many ICs,
e.g. function
f(x) { x.a.b.c = 1; } has two LoadICs and one StoreIC.)
The "full compiler" generates unoptimized code for each function the first
time it
On Tue, Sep 22, 2015 at 10:17 AM, Ignacio Queralt
wrote:
> I've read online in a Google V8 presentation that there are the following
> states regarding IC:
> Uninitialized -> Pre-monomorphic -> Monomorphic -> Polymorphic/Megamorphic
> -> Generic
> How should I build an example, or which flag shoul
Thank you both for your answers. It really helped me!
--
--
v8-users mailing list
v8-users@googlegroups.com
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
