Commit aa4a1abd authored by mstarzinger's avatar mstarzinger Committed by Commit bot

[turbofan] Remove FP-based AccessBuilder functions.

This is deprecating the ability of TurboFan to access FP-based slots
via LoadField and StoreField nodes. The corresponding constructors for
FieldAccess tuples are being removed.

R=bmeurer@chromium.org

Review URL: https://codereview.chromium.org/1512243003

Cr-Commit-Position: refs/heads/master@{#32760}
parent 2fe34ebd
......@@ -361,24 +361,6 @@ FieldAccess AccessBuilder::ForStatsCounter() {
return access;
}
// static
FieldAccess AccessBuilder::ForFrameCallerFramePtr() {
FieldAccess access = {kUntaggedBase, StandardFrameConstants::kCallerFPOffset,
MaybeHandle<Name>(), Type::Internal(),
MachineType::Pointer()};
return access;
}
// static
FieldAccess AccessBuilder::ForFrameMarker() {
FieldAccess access = {kUntaggedBase, StandardFrameConstants::kMarkerOffset,
MaybeHandle<Name>(), Type::Tagged(),
MachineType::AnyTagged()};
return access;
}
} // namespace compiler
} // namespace internal
} // namespace v8
......@@ -121,15 +121,6 @@ class AccessBuilder final : public AllStatic {
// Provides access to the backing store of a StatsCounter.
static FieldAccess ForStatsCounter();
// ===========================================================================
// Access to activation records on the stack (based on frame pointer).
// Provides access to the next frame pointer in a stack frame.
static FieldAccess ForFrameCallerFramePtr();
// Provides access to the marker in a stack frame.
static FieldAccess ForFrameMarker();
private:
DISALLOW_IMPLICIT_CONSTRUCTORS(AccessBuilder);
};
......
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