1. 30 Jun, 2014 1 commit
  2. 24 Jun, 2014 1 commit
  3. 05 Jun, 2014 1 commit
  4. 03 Jun, 2014 1 commit
  5. 29 Apr, 2014 1 commit
  6. 06 Dec, 2013 1 commit
  7. 29 Jul, 2013 1 commit
  8. 14 Jun, 2013 1 commit
  9. 10 Apr, 2013 1 commit
  10. 12 Dec, 2012 1 commit
  11. 07 Dec, 2012 1 commit
  12. 05 Apr, 2012 1 commit
  13. 27 Mar, 2012 1 commit
  14. 12 Mar, 2012 1 commit
  15. 22 Feb, 2012 1 commit
  16. 09 Feb, 2012 2 commits
  17. 13 Jan, 2012 1 commit
  18. 11 Aug, 2011 1 commit
  19. 05 Jul, 2011 1 commit
  20. 29 Jun, 2011 1 commit
    • vitalyr@chromium.org's avatar
      Suspend runtime profiler as soon as we exit JS. · 90c9f1b9
      vitalyr@chromium.org authored
      Lots of web pages have really frequently firing timers that keep the
      profiler thread spinning if we require a period of JS inactivity
      before suspending the profiler. While it's possible to throttle it by
      increasing the sleep delay and adjusting the duration of the required
      inactive period, it seemed much simpler to just stop it immediately on
      exiting JS.
      
      Stopping the profiler this way effectively turned off two optimization
      heuristics: 1) eager optimization (it's reset on waking up the
      profiler and now the profiler wakes up much more frequently) and 2)
      optimization throttling based on JS to non-JS state ratio (the ratio
      is now 100%). I removed these two heuristics and found no performance
      regressions so far.
      
      R=ager@chromium.org
      BUG=crbug.com/77625
      TEST=none
      
      Review URL: http://codereview.chromium.org/7274024
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8472 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      90c9f1b9
  21. 12 Apr, 2011 1 commit
  22. 10 Apr, 2011 1 commit
  23. 18 Mar, 2011 3 commits
  24. 02 Mar, 2011 1 commit
  25. 07 Dec, 2010 1 commit
  26. 17 Nov, 2010 1 commit
  27. 02 Jun, 2010 1 commit
  28. 10 May, 2010 1 commit
    • erik.corry@gmail.com's avatar
      First step towards making JumpTarget work on ARM. Instead · fa7c92ea
      erik.corry@gmail.com authored
      of having a list of virtual frame pointers in the jump
      target we have one virtual frame, which is the frame that
      all have to merge to to branch to that frame.  The virtual
      frame in the JumpTarget is inside the JumpTarget, rather than
      being an allocated object that is pointed to.  Unfortunately
      this means that the JumpTarget class has to be able to see
      the size of a VirtualFrame object to compile, which in turn
      lead to a major reorganization of related .h files.  The
      actual change of functionality in this change is intended
      to be minimal (we now assert that the virtual frames match
      when using JumpTarget instead of just assuming that they do).
      Review URL: http://codereview.chromium.org/1961004
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@4631 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      fa7c92ea
  29. 08 Apr, 2010 1 commit
  30. 25 Mar, 2010 1 commit
  31. 04 Feb, 2010 1 commit
  32. 27 May, 2009 1 commit
  33. 31 Mar, 2009 3 commits
  34. 27 Mar, 2009 1 commit
  35. 16 Jan, 2009 1 commit