ae764cc31b
In the {Fixed} variant, the {WasmCodeManagerTest} always reserves 1GB of memory. This makes the test run OOM on many 32-bit platforms. Instead of skipping it selectively, this CL just removes the whole test. It caused a lot of trouble in the past, and needs two test-only methods in the WasmCodeManager. Also, the {Fixed} variant will not be needed any more with the wasm far jump table, since modules can always grow then. Drive-by: Clean up the unittests status file a bit. R=mstarzinger@chromium.org Bug: v8:9477 Change-Id: I5b6f8ed9f800863575c69d49d5df82f21fd23030 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1815251 Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Clemens Backes [né Hammacher] <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#63942} |
||
---|---|---|
.. | ||
control-transfer-unittest.cc | ||
decoder-unittest.cc | ||
function-body-decoder-unittest.cc | ||
leb-helper-unittest.cc | ||
loop-assignment-analysis-unittest.cc | ||
module-decoder-unittest.cc | ||
OWNERS | ||
streaming-decoder-unittest.cc | ||
trap-handler-posix-unittest.cc | ||
trap-handler-win-unittest.cc | ||
trap-handler-x64-unittest.cc | ||
wasm-code-manager-unittest.cc | ||
wasm-compiler-unittest.cc | ||
wasm-macro-gen-unittest.cc | ||
wasm-module-builder-unittest.cc | ||
wasm-module-sourcemap-unittest.cc | ||
wasm-opcodes-unittest.cc | ||
wasm-text-unittest.cc |