• ahaas's avatar
    [wasm] Fix bounds check in LoadDataSegments. · ac183d49
    ahaas authored
    The bounds check in LoadDataSegment was off by one. I also improved the
    error message, and fixed an issue where data was initialized even if
    the bounds check failed.
    
    In InstantiateModuleForTesting I allow instantiation of modules without
    exports. This check was legacy code from the time where instantiation
    and execution was still combined in a single function.
    
    R=titzer@chromium.org, rossberg@chromium.org
    TEST=cctest/test-run-wasm-module/InitDataAtTheUpperLimit
    
    Review-Url: https://codereview.chromium.org/2486183002
    Cr-Commit-Position: refs/heads/master@{#40856}
    ac183d49
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...