1. 11 Jul, 2017 1 commit
    • Alexandre Talon's avatar
      [Turbofan] Enable reducers to report their name to make reducer tracing clearer · 7a75da34
      Alexandre Talon authored
      Each reducer now has a virtual reducer_name function, returning its name
      (the name of the class containing this reducer). This gets displayed when
      using the --trace_turbo_reduction flag. Also when using this flags more
      messages are displayed.
      
      Actually when a node is replaced in-place (which is called an update
      of the node), other reducers can still update it right after the
      in-place replacement. When a node is really replaced (not in-place),
      then we stop trying to apply reducers to it before we propagate the
      reduction through the relevant nodes.
      
      Before a message got printed only for the last reduction it went
      through. So in case a node was reduced in-place several times
      in a row, only the last update was printed, or none at all if after
      being reduced in-place it got reduced by being replaced by another
      node: only the non-in-place replacement was showed. 
      
      Now each time an in-place reduction is applied to a node, a message
      gets printed.
      
      Bug: 
      Change-Id: Id0f816fecd44c01d0253966c6decc4861be0c2fa
      Reviewed-on: https://chromium-review.googlesource.com/563365Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Commit-Queue: Alexandre Talon <alexandret@google.com>
      Cr-Commit-Position: refs/heads/master@{#46552}
      7a75da34
  2. 17 Oct, 2016 1 commit
  3. 18 Jul, 2016 1 commit
  4. 29 Jun, 2016 3 commits
  5. 01 Jun, 2016 1 commit
    • mstarzinger's avatar
      [turbofan] Implement simplistic checkpoint reducer. · 7ecf1a05
      mstarzinger authored
      This adds a very simplistic reduction of {CheckPoint} nodes via the new
      {CheckpointElimination}, eliminating redundant check points that appear
      in an effect chain of operations that are all {kNoWrite}. Such a chain
      allows an arbitrary check point to be chosen. The current approach will
      end up choosing the first one for all deopts in the chain.
      
      R=bmeurer@chromium.org
      TEST=unittests/CheckpointEliminationTest.CheckPointChain
      BUG=v8:5021
      
      Review-Url: https://codereview.chromium.org/2022913003
      Cr-Commit-Position: refs/heads/master@{#36634}
      7ecf1a05