• Andreas Haas's avatar
    [wasm] Don't call constructors directly from wasm2js wrappers · fc976f8e
    Andreas Haas authored
    For the wasm2js wrappers we have an optimization to call a JavaScript
    function directly if the signature of the JavaScript function matches
    the signature of the WebAssembly import. However, we are not supposed
    to do this optimization if the imported function is a constructor,
    because constructors can only be called with `new`. With this CL we
    do not apply this optimization when the imported function is a
    constructor.
    
    R=titzer@chromium.org
    
    Bug: chromium:824859
    Change-Id: I1722367bd865d0b129eadf7d4849182410447179
    Reviewed-on: https://chromium-review.googlesource.com/985974Reviewed-by: 's avatarBen Titzer <titzer@chromium.org>
    Commit-Queue: Andreas Haas <ahaas@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#52296}
    fc976f8e
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
fuzzer Loading commit data...
inspector Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mkgrokdump Loading commit data...
mozilla Loading commit data...
preparser Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
wasm-spec-tests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...