• ahaas's avatar
    [wasm] Change the constant kV8MaxWasmMemoryPages to a command line flag. · 94266b7d
    ahaas authored
    The hardcoded constant caused a problem for the wasm fuzzer because
    when the maximum memory was allocated in a test case, clusterfuzz ran
    out of memory. with the command line flag we can set a lower limit
    for the fuzzer.
    
    The flag has the value of the constant as its default value, so that
    for everything but the fuzzers nothing should change.
    
    R=titzer@chromium.org
    BUG=chromium:676888
    
    Review-Url: https://codereview.chromium.org/2626313003
    Cr-Commit-Position: refs/heads/master@{#42599}
    94266b7d
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...