1. 04 May, 2015 1 commit
  2. 14 Apr, 2015 4 commits
  3. 08 Apr, 2015 1 commit
  4. 07 Apr, 2015 1 commit
  5. 27 Mar, 2015 1 commit
  6. 26 Mar, 2015 1 commit
  7. 23 Mar, 2015 1 commit
    • mstarzinger's avatar
      Make compiler more acceptive wrt Isolate::use_crankshaft. · d6085f27
      mstarzinger authored
      This allows using %OptimizeFunctionOnNextCall and friends even when
      Crankshaft is disabled. Note that this should only affect code paths
      that are not relevant to performance. By now we have a single bailout
      point in place within OptimizedCompileJob::CreateGraph that ensures
      Crankshaft is only used when enabled and supported.
      
      R=titzer@chromium.org
      
      Review URL: https://codereview.chromium.org/999173007
      
      Cr-Commit-Position: refs/heads/master@{#27367}
      d6085f27
  8. 17 Mar, 2015 1 commit
  9. 04 Mar, 2015 1 commit
  10. 09 Feb, 2015 1 commit
  11. 19 Jan, 2015 1 commit
  12. 16 Jan, 2015 1 commit
  13. 02 Jan, 2015 1 commit
  14. 22 Dec, 2014 1 commit
  15. 26 Nov, 2014 1 commit
    • titzer's avatar
      Abort optimization in corner case. · 9da49982
      titzer authored
      The %OptimizeFunctionOnNextCall sledgehammer can cause a function to be
      marked for optimization before it's ever been compiled by fullcode.
      This can lead to the situation where a function doesn't have optimization
      disabled until we try to compile it optimized.
      
      Basically, the assert should just handle this case more gracefully.
      
      R=yangguo@chromium.org
      BUG=436893
      LOG=Y
      
      Review URL: https://codereview.chromium.org/760063002
      
      Cr-Commit-Position: refs/heads/master@{#25528}
      9da49982
  16. 25 Nov, 2014 1 commit
  17. 17 Nov, 2014 1 commit
  18. 05 Nov, 2014 2 commits
  19. 23 Oct, 2014 1 commit
  20. 20 Oct, 2014 3 commits
  21. 09 Oct, 2014 1 commit
  22. 30 Sep, 2014 3 commits
  23. 29 Sep, 2014 1 commit