1. 26 Dec, 2018 1 commit
  2. 17 Dec, 2018 1 commit
  3. 12 Nov, 2018 1 commit
  4. 05 Nov, 2018 1 commit
  5. 31 Oct, 2018 3 commits
  6. 24 Oct, 2018 1 commit
  7. 19 Oct, 2018 1 commit
  8. 16 Oct, 2018 1 commit
  9. 30 Jul, 2018 1 commit
  10. 23 Jul, 2018 1 commit
  11. 18 Jul, 2018 1 commit
  12. 26 Jun, 2018 1 commit
  13. 14 May, 2018 1 commit
  14. 09 May, 2018 1 commit
  15. 18 Oct, 2017 1 commit
  16. 14 Sep, 2017 1 commit
  17. 13 Sep, 2017 1 commit
  18. 11 Sep, 2017 1 commit
  19. 12 Apr, 2017 1 commit
  20. 28 Feb, 2017 1 commit
  21. 06 Feb, 2017 1 commit
    • mvstanton's avatar
      [TypeFeedbackVector] Root feedback vectors at function literal site. · aea3ce3d
      mvstanton authored
      TypeFeedbackVectors are strongly rooted by a closure. However, in modern
      JavaScript closures are created and abandoned more freely. An important
      closure may not be present in the root-set at time of garbage collection,
      even though we've cached optimized code and use it regularly. For
      example, consider leaf functions in an event dispatching system. They may
      well be "hot," but tragically non-present when we collect the heap.
      
      Until now, we've relied on a weak root to cache the feedback vector in
      this case. Since there is no way to signal intent or relative importance,
      this weak root is as susceptible to clearing as any other weak root at
      garbage collection time.
      
      Meanwhile, the feedback vector has become more important. All of our
      ICs store their data there. Literal and regex boilerplates are stored there.
      If we lose the vector, then we not only lose optimized code built from
      it, we also lose the very feedback which allowed us to create that optimized
      code. Therefore it's vital to express that dependency through the root
      set.
      
      This CL does this by creating a strong link to a feedback
      vector at the instantiation site of the function closure.
      This instantiation site is in the code and feedback vector
      of the outer closure.
      
      BUG=v8:5456
      
      Review-Url: https://codereview.chromium.org/2674593003
      Cr-Commit-Position: refs/heads/master@{#42953}
      aea3ce3d
  22. 26 Oct, 2015 3 commits
  23. 31 Aug, 2015 1 commit
    • mstarzinger's avatar
      [turbofan] Remove usage of Unique<T> from graph. · 6e65e6db
      mstarzinger authored
      The usage of Unique<T> throughout the TurboFan IR does not have any
      advantage. There is no single point in time when they are initialized
      and most use-sites looked through to the underlying Handle<T> anyways.
      Also there already was a mixture of Handle<T> versus Unique<T> in the
      graph and this unifies the situation to use Handle<T> everywhere.
      
      R=bmeurer@chromium.org,titzer@chromium.org
      
      Review URL: https://codereview.chromium.org/1314473007
      
      Cr-Commit-Position: refs/heads/master@{#30458}
      6e65e6db
  24. 15 Jul, 2015 3 commits
  25. 26 Jun, 2015 1 commit
  26. 19 Jun, 2015 2 commits
  27. 05 May, 2015 2 commits
  28. 08 Sep, 2014 1 commit
  29. 05 Aug, 2014 1 commit
  30. 04 Aug, 2014 1 commit
  31. 03 Jun, 2014 1 commit
  32. 30 Apr, 2014 1 commit