• gdeepti's avatar
    [wasm] Handle no initial memory case correctly when memory is exported · 78b8d7ed
    gdeepti authored
    Currently when the module has memory specified in the compiled bytes, but with no initial memory
    exported memory assigns a bogus buffer to the instance. When grow_memory is called on this buffer, it tries to patch an incorrect address.
     - Fix exported memory to handle no initial memory
     - Fix grow_memory to handle uninitialized buffers
    
    BUG=chromium:710844
    R=bradnelson@chromium.org
    
    Review-Url: https://codereview.chromium.org/2820223002
    Cr-Commit-Position: refs/heads/master@{#44671}
    78b8d7ed
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...
mozilla Loading commit data...
preparser Loading commit data...
promises-aplus Loading commit data...
simdjs Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
bot_default.gyp Loading commit data...
bot_default.isolate Loading commit data...
default.gyp Loading commit data...
default.isolate Loading commit data...
optimize_for_size.gyp Loading commit data...
optimize_for_size.isolate Loading commit data...
perf.gyp Loading commit data...
perf.isolate Loading commit data...