1. 23 Oct, 2017 5 commits
  2. 22 Oct, 2017 1 commit
  3. 20 Oct, 2017 11 commits
  4. 19 Oct, 2017 11 commits
    • Jaroslav Sevcik's avatar
      Revert "[turbofan] Load elimination prunes control flow based on instance type." · 8f09a751
      Jaroslav Sevcik authored
      This reverts commit 71bcc1d9.
      
      Reason for revert: Regresses Octane/Box2D, among other things.
      
      Original change's description:
      > [turbofan] Load elimination prunes control flow based on instance type.
      > 
      > Changes:
      > - introduce the notion of unreachable abstract states.
      > 
      > - reconnect unreachables states to runtime abort in effect phis (so that
      >   the merged states are not polluted by unreachable branches while
      >   preserving SSA).
      > 
      > - mark states with failed map checks, unreachable map guars as unreachable.
      > 
      > - add instance type to AbstractMaps, only invalidate instance type on
      >   mismatched effect merges.
      > 
      > 
      > This results in 2-3% improvement on ARES/ML steady state.
      > 
      > Bug: v8:6396
      > Change-Id: I35b0d4482fa400ba7ee9a754f8ef1b2663ebc7dc
      > Reviewed-on: https://chromium-review.googlesource.com/727761
      > Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
      > Commit-Queue: Jaroslav Sevcik <jarin@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#48742}
      
      TBR=jarin@chromium.org,bmeurer@chromium.org
      
      Change-Id: I6302b37dbf5ea781c64815ef1900681531ad7d71
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: v8:6396
      Reviewed-on: https://chromium-review.googlesource.com/728440Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Commit-Queue: Jaroslav Sevcik <jarin@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48763}
      8f09a751
    • Jaroslav Sevcik's avatar
      [turbofan] Check that effect control linearizations have the right value output count. · ff8b937f
      Jaroslav Sevcik authored
      Bug: v8:5267
      Change-Id: Icd56bdf58ed784747a710007ec5b99d9b756cbd7
      Reviewed-on: https://chromium-review.googlesource.com/727887Reviewed-by: 's avatarBenedikt Meurer <bmeurer@chromium.org>
      Commit-Queue: Jaroslav Sevcik <jarin@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48762}
      ff8b937f
    • Tobias Tebbi's avatar
      Revert "Reland^4 "[turbofan] eagerly prune None types and deadness from the graph"" · 2bf01995
      Tobias Tebbi authored
      This revert is manual, but almost completely automatic. 
      It was just blocked by a single-line irrelevant refactoring change.
      This reverts commit 1cee0e01.
      
      Reason for revert: chromium:776256
      
      Original change's description:
      > Reland^4 "[turbofan] eagerly prune None types and deadness from the graph"
      >
      > This fixes https://bugs.chromium.org/p/chromium/issues/detail?id=773954.
      > The issue was that in the EffectControlLinearizer, the effect input of an
      > {Unreachable} node was not updated, leaving a {Checkpoint} behind.
      >
      > This is a reland of 4cf47645
      > Original change's description:
      > > Reland^3 "[turbofan] eagerly prune None types and deadness from the graph"
      > >
      > > This fixes the issues
      > > https://bugs.chromium.org/p/chromium/issues/detail?id=772873
      > > and https://bugs.chromium.org/p/chromium/issues/detail?id=772872.
      > >
      > > One problem was that mutating an effect node into Unreachable confused
      > > the LoadElimination sidetables, so I just always create a new node now.
      > >
      > > The other problem was that UpdateBlockControl() was executed after
      > > UpdateEffectPhi() in the lazy case. This reverted the update to the Merge input.
      > > So now I make sure that UpdateEffectPhi() is always executed last.
      > >
      > > This is a reland of 6ddb5e7d
      > > Original change's description:
      > > > Reland^2 "[turbofan] eagerly prune None types and deadness from the graph"
      > > >
      > > > Now, the EffectControlLinearizer connects all occurrences of Unreachable to the
      > > > graph end. This fixes issues with later phases running DeadCodeElimination and
      > > > introducing new DeadValue nodes when processing uses of Unreachable.
      > > >
      > > > This is a reland of 3c4bc27f
      > > > Original change's description:
      > > > > Reland "[turbofan] eagerly prune None types and deadness from the graph"
      > > > >
      > > > > This is a reland of e1cdda25
      > > > > Original change's description:
      > > > > > [turbofan] eagerly prune None types and deadness from the graph
      > > > > >
      > > > > > In addition to using the {Dead} node to prune dead control nodes and nodes that
      > > > > > depend on them, we introduce a {DeadValue} node representing an impossible value
      > > > > > that can occur at any position in the graph. The extended {DeadCodeElimination}
      > > > > > prunes {DeadValue} and its uses, inserting a crashing {Unreachable} node into
      > > > > > the effect chain when possible. The remaining uses of {DeadValue} are handled
      > > > > > in {EffectControlLinearizer}, where we always have access to the effect chain.
      > > > > > In addition to explicitly introduced {DeadValue} nodes, we consider any value use
      > > > > > of a node with type {None} as dead.
      > > > > >
      > > > > > Bug: chromium:741225
      > > > > > Change-Id: Icc4b636d1d018c452ba1a2fa7cd3e00e522f1655
      > > > > > Reviewed-on: https://chromium-review.googlesource.com/641250
      > > > > > Commit-Queue: Tobias Tebbi <tebbi@chromium.org>
      > > > > > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
      > > > > > Cr-Commit-Position: refs/heads/master@{#48208}
      > > > >
      > > > > Bug: chromium:741225
      > > > > Change-Id: I21316913dae02864f7a6d7c9269405a79f054138
      > > > > Reviewed-on: https://chromium-review.googlesource.com/692034
      > > > > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
      > > > > Commit-Queue: Tobias Tebbi <tebbi@chromium.org>
      > > > > Cr-Commit-Position: refs/heads/master@{#48232}
      > > >
      > > > Bug: chromium:741225
      > > > Change-Id: I5702ec34856c075717162153adc765774453c45f
      > > > Reviewed-on: https://chromium-review.googlesource.com/702264
      > > > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
      > > > Commit-Queue: Tobias Tebbi <tebbi@chromium.org>
      > > > Cr-Commit-Position: refs/heads/master@{#48366}
      > >
      > > Bug: chromium:741225
      > > Change-Id: I4054a694d2521c2e1f0c4a3ad0f3cf100b5c536f
      > > Reviewed-on: https://chromium-review.googlesource.com/709214
      > > Commit-Queue: Tobias Tebbi <tebbi@chromium.org>
      > > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
      > > Cr-Commit-Position: refs/heads/master@{#48469}
      >
      > Bug: chromium:741225
      > Change-Id: Id9d4f3a3ae36cb3e38f80edcdba88efa7922ca24
      > Reviewed-on: https://chromium-review.googlesource.com/715716
      > Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
      > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
      > Commit-Queue: Tobias Tebbi <tebbi@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#48660}
      
      TBR=jarin@chromium.org,tebbi@chromium.org,bmeurer@chromium.org
      
      
      Bug: chromium:741225 chromium:776256
      Change-Id: Iaf2af3cb6dea5fdece43297cb9d987e7decc726d
      Reviewed-on: https://chromium-review.googlesource.com/727804
      Commit-Queue: Tobias Tebbi <tebbi@chromium.org>
      Reviewed-by: 's avatarTobias Tebbi <tebbi@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48749}
      2bf01995
    • Toon Verwaest's avatar
      [utils] Move modulo from codegen to utils · 9b88818c
      Toon Verwaest authored
      This also changes modulo to be more like others, e.g., Pow:
      - have an inline Modulo
      - have a modulo_double_double that we can use as FUNCTION_ADDR in assembler.cc
      
      Bug: 
      Change-Id: Id360e4adcde5712ffc5ac22abd3bbaab6aec09f5
      Reviewed-on: https://chromium-review.googlesource.com/728027
      Commit-Queue: Toon Verwaest <verwaest@chromium.org>
      Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48747}
      9b88818c
    • Jaroslav Sevcik's avatar
      [turbofan] Load elimination prunes control flow based on instance type. · 71bcc1d9
      Jaroslav Sevcik authored
      Changes:
      - introduce the notion of unreachable abstract states.
      
      - reconnect unreachables states to runtime abort in effect phis (so that
        the merged states are not polluted by unreachable branches while
        preserving SSA).
      
      - mark states with failed map checks, unreachable map guars as unreachable.
      
      - add instance type to AbstractMaps, only invalidate instance type on
        mismatched effect merges.
      
      
      This results in 2-3% improvement on ARES/ML steady state.
      
      Bug: v8:6396
      Change-Id: I35b0d4482fa400ba7ee9a754f8ef1b2663ebc7dc
      Reviewed-on: https://chromium-review.googlesource.com/727761Reviewed-by: 's avatarBenedikt Meurer <bmeurer@chromium.org>
      Commit-Queue: Jaroslav Sevcik <jarin@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48742}
      71bcc1d9
    • Mike Stanton's avatar
      [Turbofan] Introduce StringToNumber opcode · d3797add
      Mike Stanton authored
      If we have good lower bound type information in simplified lowering
      that the input to PlainPrimitiveToNumber is a string, then we'd like
      to introduce a call to the StringToNumber builtin. However, this
      requires more careful management of the effect chain than we had
      previously. To fix this, introduce a StringToNumber opcode which
      defers the graph alteration until effect-control-linearization,
      when the effect chain is available for careful wiring.
      
      Bug: v8:6929
      Change-Id: I4f0e43fe474a44d0dfa095a3a01caece649d82db
      Reviewed-on: https://chromium-review.googlesource.com/727934Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Commit-Queue: Michael Stanton <mvstanton@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48741}
      d3797add
    • Michael Starzinger's avatar
      [runtime] Allocate DeoptimizationData before Code objects. · 52d54f7c
      Michael Starzinger authored
      This allocates and populates potential deoptimization data arrays before
      the underlying {Code} objects is allocated. It aims at making the field
      holding said data immutable after allocation. Note that we still mutate
      this field during deoptimization.
      
      R=verwaest@chromium.org
      BUG=v8:6792
      
      Change-Id: Id0c2cfb65e782d7292d2df6bff41c54b2b8c3351
      Reviewed-on: https://chromium-review.googlesource.com/725704Reviewed-by: 's avatarToon Verwaest <verwaest@chromium.org>
      Commit-Queue: Michael Starzinger <mstarzinger@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48738}
      52d54f7c
    • Mike Stanton's avatar
      [Turbofan] Model JSToBoolean as a simplified operator · 78fc6668
      Mike Stanton authored
      Because the toboolean operator may lower to a builtin call (which is
      effectful in turbofan parlance after effect control linearization),
      it really should be encoded as a simplified operator, which can
      be optimized with respect for the effect chain in linearization.
      
      No new functionality here, rather a furniture rearrangement in
      the TurboFan node structure.
      
      Bug: v8:6929
      Change-Id: I371fd22941397d5c28d13bded2738161d8da8275
      Reviewed-on: https://chromium-review.googlesource.com/725721Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Commit-Queue: Michael Stanton <mvstanton@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48727}
      78fc6668
    • Benedikt Meurer's avatar
      [ic] Teach CallIC about JSBoundFunction. · e57a99ce
      Benedikt Meurer authored
      This addresses the odd performance cliff, where the CallIC tracks known
      JSFunction targets, but goes MEGAMORPHIC when it sees a JSBoundFunction
      target. With this fix in place the micro-benchmark on the bug goes from
      
        arrowCall: 82 ms.
        boundCall: 234 ms.
      
      to
      
        arrowCall: 81 ms.
        boundCall: 80 ms.
      
      so Function#bind doesn't cause any additional overhead anymore.
      
      Bug: v8:5267, v8:6962
      Change-Id: Iaceaf89fd3e99e2afe2ae45e96a6813a3ef8b1d2
      Reviewed-on: https://chromium-review.googlesource.com/727879
      Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
      Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48722}
      e57a99ce
    • Benedikt Meurer's avatar
      [turbofan] Unfold bound functions at call sites. · 99100db4
      Benedikt Meurer authored
      So far the JSCallReducer was only able to unfold constant
      JSBoundFunction targets for JSCall nodes, which is not the
      common case. With the introduction of JSCreateBoundFunction
      operator earlier, we can now also recognize calls to bound
      functions where the bind happens earlier in the function,
      i.e. as the example of
      
        a.map(f.bind(self))
      
      in https://twitter.com/BenLesh/status/920700003974123520, which
      is a handy way to use Function#bind. So this transformation
      takes a node like
      
        JSCall(JSCreateBoundFunction(bound_target_function,
                                     bound_this,
                                     a1,...,aN),
               receiver, p1,...,pM)
      
      and turns that into
      
        JSCall(bound_target_function, bound_this, a1,...,aN,p1,...,pM)
      
      allowing TurboFan to further inline the bound_target_function
      at this call site if that's also inlinable (i.e. it's a known
      constant JSFunction or the result of a JSCreateClosure call).
      
      This improves the micro-benchmark from
      
        arrowCall: 55 ms.
        boundCall: 221 ms.
        arrowMap: 181 ms.
        boundMap: 806 ms.
      
      to
      
        arrowCall: 71 ms.
        boundCall: 76 ms.
        arrowMap: 188 ms.
        boundMap: 186 ms.
      
      so that Function#bind in this case is as fast as using closures,
      which is an up to 4.3x improvement in the Array#map example.
      
      Bug: v8:5257, v8:6961
      Change-Id: Ibca650faad912bf9db1db6fbc48772e7551289a6
      Reviewed-on: https://chromium-review.googlesource.com/727799Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48713}
      99100db4
    • Junliang Yan's avatar
      PPC: fix constant pool issue in OutOfLineRecordWrite · 81c67751
      Junliang Yan authored
      R=joransiu@ca.ibm.com, jbarboza@ca.ibm.com, michael_dawson@ca.ibm.com
      
      Bug: 
      Change-Id: I38688c2168cfe6b1a2baca5ca46726cf3557634b
      Reviewed-on: https://chromium-review.googlesource.com/727139Reviewed-by: 's avatarJoran Siu <joransiu@ca.ibm.com>
      Commit-Queue: Junliang Yan <jyan@ca.ibm.com>
      Cr-Commit-Position: refs/heads/master@{#48709}
      81c67751
  5. 18 Oct, 2017 12 commits