abd024b5f3
Rename the '--wasm-max-code-space' flag to '--wasm-max-committed-code-mb'. We will introduce a new flag to set the maximum size of a wasm code space, so the old name would be misleadingly close to the new flag. R=jkummerow@chromium.org Bug: v8:13436 Change-Id: I7a86300e4f25858add1a62f9989189035ea855ef Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4022709 Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#84242}
18 lines
634 B
JavaScript
18 lines
634 B
JavaScript
// Copyright 2018 the V8 project authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style license that can be
|
|
// found in the LICENSE file.
|
|
|
|
// Flags: --wasm-max-committed-code-mb=1
|
|
|
|
d8.file.execute('test/mjsunit/wasm/wasm-module-builder.js');
|
|
|
|
// We only have 1 MB code space. This is enough for the code below, but for all
|
|
// 1000 modules, it requires several GCs to get rid of the old code.
|
|
const builder = new WasmModuleBuilder();
|
|
builder.addFunction('main', kSig_i_i).addBody([kExprLocalGet, 0]);
|
|
const buffer = builder.toBuffer();
|
|
|
|
for (let i = 0; i < 1000; ++i) {
|
|
new WebAssembly.Module(buffer);
|
|
}
|