2970249a72
The `compiler-trace-flags.js` test just makes sure the various --trace-turbo* flags do not cause V8 to crash. However, on builds with no snapshot, they would generate a *lot* of output as they were tracing the compiler while generating the snapshot. Let's set the `--trace-turbo-filter` flag to make sure we only trace the test functions. Sadly, WASM functions do not have a name, just an index, so we have to split this test into two. Bug: chromium:943064 Cq-Include-Trybots: luci.v8.try:v8_win_nosnap_shared_rel_ng Change-Id: I30b3935f63d412ab8c96cc5156d342c428229865 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1532078 Reviewed-by: Sigurd Schneider <sigurds@chromium.org> Commit-Queue: Pierre Langlois <pierre.langlois@arm.com> Cr-Commit-Position: refs/heads/master@{#60383}
31 lines
956 B
JavaScript
31 lines
956 B
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.
|
|
|
|
// Disable liftoff to make sure we generate turbofan traces.
|
|
// Flags: --no-liftoff
|
|
// Flags: --trace-turbo --trace-turbo-graph
|
|
// Flags: --trace-turbo-cfg-file=test/mjsunit/tools/turbo.cfg
|
|
// Flags: --trace-turbo-path=test/mjsunit/tools
|
|
|
|
// Only trace the wasm functions:
|
|
// Flags: --trace-turbo-filter=wasm*
|
|
|
|
load('test/mjsunit/wasm/wasm-module-builder.js');
|
|
|
|
// The idea behind this test is to make sure we do not crash when using the
|
|
// --trace-turbo flag given different sort of inputs.
|
|
|
|
(function testWASM() {
|
|
let builder = new WasmModuleBuilder();
|
|
|
|
builder.addFunction("add", kSig_i_ii)
|
|
.addBody([kExprGetLocal, 0,
|
|
kExprGetLocal, 1,
|
|
kExprI32Add])
|
|
.exportFunc();
|
|
|
|
let instance = builder.instantiate();
|
|
instance.exports.add(21, 21);
|
|
})();
|