-
Clemens Backes authored
This unifies {max_initial_mem_pages} and {max_maximum_mem_pages} into {max_mem_pages}. The {CompilationEnv} constructor was incorrectly using the former instead of the latter anyway. This did not really matter though, since they typically have the same value. Also, there is not a single test that sets --wasm-max-mem-pages-growth. R=manoskouk@chromium.org CC=jkummerow@chromium.org Bug: v8:10949 Change-Id: Ib7ab9b4c239d50b72013087eda5a214829c90369 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2426619Reviewed-by:Manos Koukoutos <manoskouk@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#70114}
5f265c33
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| api | Loading commit data... | |
| asmjs | ||
| ast | ||
| base | ||
| builtins | ||
| codegen | ||
| common | ||
| compiler | ||
| compiler-dispatcher | ||
| d8 | ||
| date | ||
| debug | ||
| deoptimizer | ||
| diagnostics | ||
| execution | ||
| extensions | ||
| flags | ||
| handles | ||
| heap | ||
| ic | ||
| init | ||
| inspector | ||
| interpreter | ||
| json | ||
| libplatform | ||
| libsampler | ||
| logging | ||
| numbers | ||
| objects | ||
| parsing | ||
| profiler | ||
| protobuf | ||
| regexp | ||
| roots | ||
| runtime | ||
| sanitizer | ||
| snapshot | ||
| strings | ||
| tasks | ||
| third_party | ||
| torque | ||
| tracing | ||
| trap-handler | ||
| utils | ||
| wasm | ||
| zone | ||
| DEPS | ||
| OWNERS |