4976642bbd
FLAG_wasm_dynamic_tiering is still off by default. When enabled, it now uses the technique previously behind --new-wasm-dynamic-tiering. Bug: v8:12281 Change-Id: I365c2c066e62418cd6abc7830f95d1fe0f950e33 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3275570 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#77883}
40 lines
1.2 KiB
JavaScript
40 lines
1.2 KiB
JavaScript
// Copyright 2019 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: --allow-natives-syntax --wasm-dynamic-tiering --liftoff
|
|
// Flags: --no-wasm-tier-up --no-stress-opt
|
|
// Make the test faster:
|
|
// Flags: --wasm-tiering-budget=1000
|
|
|
|
// This test busy-waits for tier-up to be complete, hence it does not work in
|
|
// predictable more where we only have a single thread.
|
|
// Flags: --no-predictable
|
|
|
|
d8.file.execute('test/mjsunit/wasm/wasm-module-builder.js');
|
|
|
|
const num_functions = 2;
|
|
|
|
const builder = new WasmModuleBuilder();
|
|
for (let i = 0; i < num_functions; ++i) {
|
|
let kFunction = builder.addFunction('f' + i, kSig_i_v)
|
|
.addBody(wasmI32Const(i))
|
|
.exportAs('f' + i)
|
|
}
|
|
|
|
let instance = builder.instantiate();
|
|
|
|
// The first few calls happen with Liftoff code.
|
|
for (let i = 0; i < 3; ++i) {
|
|
instance.exports.f0();
|
|
instance.exports.f1();
|
|
}
|
|
assertTrue(%IsLiftoffFunction(instance.exports.f0));
|
|
assertTrue(%IsLiftoffFunction(instance.exports.f1));
|
|
|
|
// Keep calling the function until it gets tiered up.
|
|
while (%IsLiftoffFunction(instance.exports.f1)) {
|
|
instance.exports.f1();
|
|
}
|
|
assertTrue(%IsLiftoffFunction(instance.exports.f0));
|