• Clemens Hammacher's avatar
    [wasm] Fix wrong implication · 08fc24b9
    Clemens Hammacher authored
    The implication was actually in the wrong direction: If there is no
    memory start address, then the size must be 0.
    If the size is 0 though, we might allocate nevertheless to have guard
    pages around the accessible memory.
    
    R=ahaas@chromium.org
    BUG=chromium:736584
    
    Change-Id: I297dece658d5eaf69c58ecb109ff21d3ca0b8a8d
    Reviewed-on: https://chromium-review.googlesource.com/548635Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
    Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#46221}
    08fc24b9
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...
promises-aplus 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...
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...