We noticed that almost every call site were loading both files, the split isn't necessary anymore. In some message tests, removed the absolute line number to allow future changes. Bug: v8:8726 Change-Id: I8527f0a1ecfa685aa01a5e2f5f47ddf1cb13a545 Reviewed-on: https://chromium-review.googlesource.com/c/1446452 Commit-Queue: Sven Sauleau <ssauleau@igalia.com> Reviewed-by: Ben Titzer <titzer@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#59220}
28 lines
988 B
JavaScript
28 lines
988 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: --allow-natives-syntax --liftoff --wasm-trap-handler
|
|
|
|
// A simple test to make sure Liftoff can compile memory operations with trap
|
|
// handlers enabled.
|
|
|
|
load("test/mjsunit/wasm/wasm-module-builder.js");
|
|
|
|
function testCompileLoadStore() {
|
|
const builder = new WasmModuleBuilder();
|
|
// These functions generate statically out of bounds accesses.
|
|
builder.addFunction("load", kSig_i_i)
|
|
.addBody([kExprGetLocal, 0, kExprI32LoadMem, 0, 0x80, 0x80, 0x80, 1])
|
|
.exportFunc();
|
|
builder.addFunction("store", kSig_i_ii)
|
|
.addBody([kExprGetLocal, 0,
|
|
kExprGetLocal, 1,
|
|
kExprI32StoreMem, 0, 0x80, 0x80, 0x80, 1,
|
|
kExprGetLocal, 1])
|
|
.exportFunc();
|
|
builder.addMemory(1, 1, false);
|
|
const instance = builder.instantiate();
|
|
}
|
|
testCompileLoadStore();
|