1. 02 Dec, 2015 1 commit
  2. 30 Nov, 2015 1 commit
  3. 12 Nov, 2015 1 commit
  4. 05 Nov, 2015 1 commit
  5. 28 Oct, 2015 1 commit
  6. 19 Oct, 2015 1 commit
  7. 16 Oct, 2015 1 commit
    • mstarzinger's avatar
      [turbofan] Move SimplifiedOperatorBuilder into JSGraph. · b7990793
      mstarzinger authored
      This fixes the lifetime of nodes created by JSGlobalSpecialization that
      contain a simplified operator. In the case where this reducer runs as
      part of the inliner, the SimplifiedOperatorBuilder was instantiated with
      the wrong zone. This led to use-after-free of simplified operators.
      
      To avoid such situations in the future, we decided to move this operator
      builder into the JSGraph and make the situation uniform with all other
      operator builders.
      
      R=bmeurer@chromium.org
      BUG=chromium:543528
      LOG=n
      
      Review URL: https://codereview.chromium.org/1409993002
      
      Cr-Commit-Position: refs/heads/master@{#31334}
      b7990793
  8. 29 Sep, 2015 1 commit
  9. 04 Sep, 2015 1 commit
  10. 13 Aug, 2015 2 commits
  11. 23 Jun, 2015 1 commit
  12. 15 Jun, 2015 1 commit
  13. 05 Jun, 2015 1 commit
    • mstarzinger's avatar
      [turbofan] Allow ReplaceWithValue to kill control. · 8f4d9a0a
      mstarzinger authored
      This allows any AdvancedReducer to remove exception projections from
      graphs. This is the common case when JS-operators are being replaced
      with pure values. The old NodeProperties::ReplaceWithValue is being
      deprecated in favor of AdvancedReducer::ReplaceWithValue.
      
      R=titzer@chromium.org
      TEST=unittests/AdvancedReducerTest
      
      Review URL: https://codereview.chromium.org/1168693002
      
      Cr-Commit-Position: refs/heads/master@{#28810}
      8f4d9a0a
  14. 26 May, 2015 1 commit
  15. 20 May, 2015 1 commit
  16. 19 May, 2015 1 commit
  17. 27 Apr, 2015 1 commit
  18. 23 Apr, 2015 1 commit
    • bmeurer's avatar
      [turbofan] Unify frame state inputs. · 4940c0bd
      bmeurer authored
      Now all nodes that care about deoptimization always take frame state
      inputs no matter whether deoptimization is enabled for a particular
      function. In case that deoptimization is off, the AstGraphBuilder just
      inserts the empty frame state. This greatly simplifies the logic in
      various places and makes testing easier as well, and is probably the
      first step towards enabling --turbo-deoptimization by default.
      
      There seems to be no noticable performance impact on asm.js programs.
      
      Also fix the graph replay in order to regenerate the scheduler unittests.
      
      Review URL: https://codereview.chromium.org/1106613003
      
      Cr-Commit-Position: refs/heads/master@{#28026}
      4940c0bd
  19. 21 Apr, 2015 1 commit
  20. 20 Apr, 2015 1 commit
  21. 02 Apr, 2015 1 commit
  22. 31 Mar, 2015 1 commit
  23. 20 Mar, 2015 2 commits
  24. 06 Mar, 2015 1 commit
  25. 05 Mar, 2015 1 commit
  26. 26 Jan, 2015 1 commit