Commit 2deeeb35 authored by Clemens Hammacher's avatar Clemens Hammacher Committed by Commit Bot

[wasm] Remove dead kInstructionStartOffset

Since the Liftoff prologue is gone (https://crrev.com/c/1110222), this
field is dead.

R=mstarzinger@chromium.org

Bug: v8:6600
Change-Id: I9d3e94a63087e7111939523c11fba4f009cecd54
Reviewed-on: https://chromium-review.googlesource.com/1116963Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#54059}
parent 6d20218e
......@@ -156,11 +156,6 @@ class V8_EXPORT_PRIVATE WasmCode final {
enum FlushICache : bool { kFlushICache = true, kNoFlushICache = false };
// Offset of {instructions_.start()}. It is used for tiering, when
// we check if optimized code is available during the prologue
// of Liftoff-compiled code.
static constexpr int kInstructionStartOffset = 0;
private:
friend class NativeModule;
......@@ -187,7 +182,6 @@ class V8_EXPORT_PRIVATE WasmCode final {
DCHECK_LE(safepoint_table_offset, instructions.size());
DCHECK_LE(constant_pool_offset, instructions.size());
DCHECK_LE(handler_table_offset, instructions.size());
DCHECK_EQ(kInstructionStartOffset, OFFSET_OF(WasmCode, instructions_));
}
// Code objects that have been registered with the global trap handler within
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment