PPC: [turbofan] Add general support for sp-based frame access

PPC: [turbofan] Add general support for sp-based frame access

Port 51669873694ed266ea06a2726f87138374eea1e7

Original commit message:
    Some highlights of this CL:
    * Refactor the mutable state out of Frame into FrameAccessState,
      which is maintained and updated during code generation to
      record whether sp- or fp-based frame access is currently active
      and how deep the stack on top of the frame is.
    * The operand resultion in linkage.cc now uses FrameAccessState
      to determine how to generate frame-accessing operands.
    * Update all platforms to accurately track additionally pushed
      stack slots (e.g. arguments for calls) in the FrameAccessState.
    * Add a flag, --turbo_sp_frame_access, which forces all frame
      access to be sp-based whenever possible. This will likely never
      be used in production, but for testing it's useful in verifying
      that the stack-tracking of each platform maintained in the
      FrameAccessState is correct.
    * Use sp-based frame access for gap resolving before tail
      calls. This will allow for slightly more efficient restoration
      of the frame pointer in the tail call in a later CL.
    * Remove most ad hoc groping into CallDescriptors to
      determine if a frame is needed, instead consistently use
      predicates like needs_frame(), IsCFunctionCall() and
      IsJSFunctionCall().

R=danno@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
BUG=v8:4076
LOG=n

Committed: https://crrev.com/19f33159986746e84a886c09b442751001e0496e
Cr-Commit-Position: refs/heads/master@{#32420}

[michael_dawson, 2015-11-30 21:25:33]

On 2015/11/30 20:57:41, mtbrandyberry wrote:

lgtm

[MTBrandyberry, 2015-11-30 21:26:32]

The CQ bit was checked by mbrandy@us.ibm.com

[commit-bot: I haz the power, 2015-11-30 21:26:36]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1484913003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1484913003/1

[commit-bot: I haz the power, 2015-11-30 22:08:17]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-11-30 22:08:51]

Description was changed from

==========
PPC: [turbofan] Add general support for sp-based frame access

Port 51669873694ed266ea06a2726f87138374eea1e7

Original commit message:
    Some highlights of this CL:
    * Refactor the mutable state out of Frame into FrameAccessState,
      which is maintained and updated during code generation to
      record whether sp- or fp-based frame access is currently active
      and how deep the stack on top of the frame is.
    * The operand resultion in linkage.cc now uses FrameAccessState
      to determine how to generate frame-accessing operands.
    * Update all platforms to accurately track additionally pushed
      stack slots (e.g. arguments for calls) in the FrameAccessState.
    * Add a flag, --turbo_sp_frame_access, which forces all frame
      access to be sp-based whenever possible. This will likely never
      be used in production, but for testing it's useful in verifying
      that the stack-tracking of each platform maintained in the
      FrameAccessState is correct.
    * Use sp-based frame access for gap resolving before tail
      calls. This will allow for slightly more efficient restoration
      of the frame pointer in the tail call in a later CL.
    * Remove most ad hoc groping into CallDescriptors to
      determine if a frame is needed, instead consistently use
      predicates like needs_frame(), IsCFunctionCall() and
      IsJSFunctionCall().

R=danno@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com,
michael_dawson@ca.ibm.com
BUG=v8:4076
LOG=n
==========

to

==========
PPC: [turbofan] Add general support for sp-based frame access

Port 51669873694ed266ea06a2726f87138374eea1e7

Original commit message:
    Some highlights of this CL:
    * Refactor the mutable state out of Frame into FrameAccessState,
      which is maintained and updated during code generation to
      record whether sp- or fp-based frame access is currently active
      and how deep the stack on top of the frame is.
    * The operand resultion in linkage.cc now uses FrameAccessState
      to determine how to generate frame-accessing operands.
    * Update all platforms to accurately track additionally pushed
      stack slots (e.g. arguments for calls) in the FrameAccessState.
    * Add a flag, --turbo_sp_frame_access, which forces all frame
      access to be sp-based whenever possible. This will likely never
      be used in production, but for testing it's useful in verifying
      that the stack-tracking of each platform maintained in the
      FrameAccessState is correct.
    * Use sp-based frame access for gap resolving before tail
      calls. This will allow for slightly more efficient restoration
      of the frame pointer in the tail call in a later CL.
    * Remove most ad hoc groping into CallDescriptors to
      determine if a frame is needed, instead consistently use
      predicates like needs_frame(), IsCFunctionCall() and
      IsJSFunctionCall().

R=danno@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com,
michael_dawson@ca.ibm.com
BUG=v8:4076
LOG=n

Committed: https://crrev.com/19f33159986746e84a886c09b442751001e0496e
Cr-Commit-Position: refs/heads/master@{#32420}
==========

[commit-bot: I haz the power, 2015-11-30 22:08:52]

Patchset 1 (id:??) landed as
https://crrev.com/19f33159986746e84a886c09b442751001e0496e
Cr-Commit-Position: refs/heads/master@{#32420}