Changes between Version 8 and Version 9 of JavaScriptCore


Ignore:
Timestamp:
Sep 12, 2013 11:33:05 AM (7 years ago)
Author:
fpizlo@apple.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • JavaScriptCore

    v8 v9  
    99== Core Engine ==
    1010
    11 JavaScriptCore is an optimizing virtual machine.  JavaScriptCore consists of the following building blocks: lexer, parser, start-up interpreter ('''LLInt'''), baseline JIT, and an optimizing JIT ('''DFG''').
     11JavaScriptCore is an optimizing virtual machine.  JavaScriptCore consists of the following building blocks: lexer, parser, start-up interpreter ('''LLInt'''), baseline JIT, a low-latency optimizing JIT ('''DFG'''), and a high-throughput optimizing JIT ('''FTL''').
    1212
    1313'''Lexer''' is responsible for the [http://en.wikipedia.org/wiki/Lexical_analysis lexical analysis], i.e. breaking down the script source into a series of ''tokens''. JavaScriptCore lexer is hand-written, it is mostly in [http://trac.webkit.org/browser/trunk/Source/JavaScriptCore/parser/Lexer.h parser/Lexer.h] and [http://trac.webkit.org/browser/trunk/Source/JavaScriptCore/parser/Lexer.cpp parser/Lexer.cpp].
     
    2323
    2424'''DFG JIT''' kicks in for functions that are invoked at least 60 times, or that took a loop at least 1000 times.  Again, these numbers are approximate and are subject to additional heuristics.  The DFG performs aggressive type speculation based on profiling information collected by the lower tiers.  This allows it to forward-propagate type information, eliding many type checks.  Sometimes the DFG goes further and speculates on values themselves - for example it may speculate that a value loaded from the heap is always some known function in order to enable inlining.  The DFG uses deoptimization (we call it "OSR exit") to handle cases where speculation fails.  Deoptimization may be synchronous (for example, a branch that checks that the type of a value is that which was expected) or asynchronous (for example, the runtime may observe that the shape or value of some object or variable has changed in a way that contravenes assumptions made by the DFG).  The latter is referred to as "watchpointing" in the DFG codebase.  Altogether, the Baseline JIT and the DFG JIT share a two-way OSR relationship: the Baseline JIT may OSR into the DFG when a function gets hot, and the DFG may OSR to the Baseline JIT in the case of deoptimization.  Repeated OSR exits from the DFG serve as an additional profiling hint: the DFG OSR exit machinery records the reason of the exit (including potentially the values that failed speculation) as well as the frequency with which it occurred; if an exit is taken often enough then reoptimization kicks in: callers are relinked to the Baseline JIT for the affected function, more profiling is gathered, and then the DFG may be later reinvoked.  Reoptimization uses exponential back-off to defend against pathological code.  The DFG is in [http://trac.webkit.org/browser/trunk/Source/JavaScriptCore/dfg dfg/].
     25
     26'''FTL JIT''' kicks in for functions that are invoked thousands of times, or loop tens of thousands of times.  It is still a work in progress and is disabled by default.  See [wiki:FTLJIT] for more information.
    2527
    2628At any time, functions, eval blocks, and global code in JavaScriptCore may be executing in a mix of the LLInt, Baseline JIT, and DFG.  In the extreme case of a recursive function, there may even be multiple stack frames where one frame is in the LLInt, another is in the Baseline JIT, while another still is in the DFG; even more extreme are cases where one stack frame is executing an old DFG compilation and another is executing a new DFG compilation because recompilation kicked in but execution did not yet return to the old DFG code.  These three engines are designed to maintain identical execution semantics, and so even if multiple functions in a JavaScript program are executing in a mix of these engines the only perceptible effect ought to be execution performance.