• mtrofin's avatar
    [wasm] Compilation/Instantiation pipeline works off module object · 8e5ac62d
    mtrofin authored
    Moved the compilation/instantiation pipeline to work off the
    module object (JSObject), making the compiled module data (the
    FixedArray) an implementation detail. This:
    - simplifies the code by removing duplicate decode->compile->instantiate
    sequences
    - sets up the stage for "dressing up" the runtime model with
    stronger typed APIs
    - helps relanding this CL: https://codereview.chromium.org/2305903002/.
      It turns out that GCs during the cloning/instantiation events cause
    trouble, and centering the source of truth on the module object helps
    address this issue.
    
    In the process, clarified cctest setup for wasm-capable isolates,
    and changed signatures for consistency (using ModuleOrigin througout).
    
    BUG=
    
    Review-Url: https://codereview.chromium.org/2320723005
    Cr-Commit-Position: refs/heads/master@{#39360}
    8e5ac62d
Name
Last commit
Last update
..
json Loading commit data...
parser Loading commit data...
regexp Loading commit data...
wasm_code Loading commit data...
DEPS Loading commit data...
fuzzer-support.cc Loading commit data...
fuzzer-support.h Loading commit data...
fuzzer.cc Loading commit data...
fuzzer.gyp Loading commit data...
fuzzer.isolate Loading commit data...
fuzzer.status Loading commit data...
json.cc Loading commit data...
parser.cc Loading commit data...
regexp.cc Loading commit data...
testcfg.py Loading commit data...
wasm-asmjs.cc Loading commit data...
wasm-code.cc Loading commit data...
wasm.cc Loading commit data...
wasm.tar.gz.sha1 Loading commit data...
wasm_asmjs.tar.gz.sha1 Loading commit data...