• 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...
build_overrides Loading commit data...
docs Loading commit data...
gni Loading commit data...
gypfiles Loading commit data...
include Loading commit data...
infra Loading commit data...
samples Loading commit data...
src Loading commit data...
test Loading commit data...
testing Loading commit data...
third_party Loading commit data...
tools Loading commit data...
.clang-format Loading commit data...
.gitignore Loading commit data...
.gn Loading commit data...
.ycm_extra_conf.py Loading commit data...
AUTHORS Loading commit data...
BUILD.gn Loading commit data...
CODE_OF_CONDUCT.md Loading commit data...
ChangeLog Loading commit data...
DEPS Loading commit data...
LICENSE Loading commit data...
LICENSE.fdlibm Loading commit data...
LICENSE.strongtalk Loading commit data...
LICENSE.v8 Loading commit data...
LICENSE.valgrind Loading commit data...
Makefile Loading commit data...
Makefile.android Loading commit data...
OWNERS Loading commit data...
PRESUBMIT.py Loading commit data...
README.md Loading commit data...
WATCHLISTS Loading commit data...
codereview.settings Loading commit data...
snapshot_toolchain.gni Loading commit data...