b177b4e3e8
With statically in-bounds memory accesses (implemented in https://crrev.com/c/2919827) we would only have an offset but no index register for {TraceMemoryOperation}. This CL fixes that situation. R=thibaudm@chromium.org Bug: chromium:1248024 Change-Id: I856b263a560cb71791c61e446e78dd99c9664190 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3149464 Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#76763}
21 lines
630 B
JavaScript
21 lines
630 B
JavaScript
// Copyright 2021 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: --liftoff-only --trace-wasm-memory
|
|
|
|
d8.file.execute('test/mjsunit/wasm/wasm-module-builder.js');
|
|
|
|
const builder = new WasmModuleBuilder();
|
|
builder.addMemory(16, 17);
|
|
// Generate function 1 (out of 3).
|
|
builder.addFunction('load', kSig_i_v)
|
|
.addBody([
|
|
// body:
|
|
kExprI32Const, 0, // i32.const
|
|
kExprI32LoadMem8U, 0, 5, // i32.load8_u
|
|
])
|
|
.exportFunc();
|
|
const instance = builder.instantiate();
|
|
instance.exports.load();
|