1. 13 Apr, 2012 1 commit
  2. 05 Apr, 2012 1 commit
  3. 30 Mar, 2012 1 commit
    • danno@chromium.org's avatar
      Fix performance regressions due to lazy initialization. · 63f03357
      danno@chromium.org authored
      This CL:
      - Adds a new trait parameter to LazyInstance to let it initialize the instance
        without paying the cost of atomic operations (which are expensive on Mac).
        This only works for users who don't care about thread-safety and this is now
      the default initialization trait used by LazyInstance in v8.
      
      - Reverts the changes that were made in r11010 in isolate.{cc,h}. That lets
        Isolate's accessors be as cheap as they were before (but adds one static initializer).
      
      - Adds OS::PostSetup() used to initialize the math functions which depend on CPU features.
      That lets the math functions get rid of CallOnce().
      
      BUG=118686
      
      Review URL: https://chromiumcodereview.appspot.com/9873023
      Patch from Philippe Liard <pliard@chromium.org>.
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@11198 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      63f03357
  4. 12 Mar, 2012 1 commit
  5. 23 Feb, 2012 1 commit
  6. 20 Feb, 2012 1 commit
  7. 20 Jan, 2012 1 commit
  8. 16 Jan, 2012 1 commit
  9. 13 Jan, 2012 1 commit
  10. 08 Sep, 2011 1 commit
  11. 02 Aug, 2011 1 commit
  12. 13 Jul, 2011 1 commit
  13. 11 Jul, 2011 1 commit
  14. 05 Jul, 2011 1 commit
  15. 10 Jun, 2011 1 commit
    • mikhail.naganov@gmail.com's avatar
      "Deiceolate" Thread classes. · 508b22c4
      mikhail.naganov@gmail.com authored
      Thread class was receiving an isolate parameter by default.
      This approact violates the assumption that only VM threads
      can have an associated isolate, and can lead to troubles,
      because accessing the same isolate from different threads
      leads to race conditions.
      
      This was found by investigating mysterious failures of the
      CPU profiler layout test on Linux Chromium. As almost all
      threads were associated with some isolate, the sampler was
      trying to sample them.
      
      As a side effect, we have also fixed the DebuggerAgent test.
      
      Thanks to Vitaly for help in fixing isolates handling!
      
      R=vitalyr@chromium.org
      BUG=none
      TEST=none
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8259 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      508b22c4
  16. 11 Apr, 2011 1 commit
  17. 30 Mar, 2011 1 commit
  18. 21 Mar, 2011 1 commit
  19. 18 Mar, 2011 3 commits
  20. 21 Feb, 2011 1 commit
  21. 17 Feb, 2011 1 commit
  22. 19 Jan, 2011 3 commits
  23. 04 Jan, 2011 1 commit
  24. 08 Dec, 2010 1 commit
  25. 07 Dec, 2010 4 commits
  26. 25 Nov, 2010 1 commit
  27. 03 Nov, 2010 1 commit
  28. 02 Nov, 2010 1 commit
  29. 27 Oct, 2010 1 commit
  30. 26 Oct, 2010 1 commit
  31. 19 Oct, 2010 1 commit
    • vitalyr@chromium.org's avatar
      Support profiling based on linux kernel performance events. · e6b33bd2
      vitalyr@chromium.org authored
      Since 2.6.31 perf_events interface has been available in the
      kernel. There's a nice tool called "perf" (linux-2.6/tools/perf) that
      uses this interface and provides capabilities similar to oprofile. The
      simplest form of its usage is just dumping the raw log (trace) of
      events generated by the kernel. In this patch I'm adding a script
      (tools/ll_prof.py) to build profiles based on perf trace and our code
      log. All the heavy-lifting is done by perf. Compared to oprofile agent
      this approach does not require recompilation and supports code moving
      garbage collections.
      
      Expected usage is documented in the ll_prof's help. Basically one
      should run V8 under perf passing --ll-prof flag and then the produced
      logs can be analyzed by tools/ll_prof.py.
      
      The new --ll-prof flag enables logging of generated code object
      locations and names (like --log-code), and also of their bodies, which
      can be later disassembled and annotated by the script.
      
      Review URL: http://codereview.chromium.org/3831002
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5663 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      e6b33bd2
  32. 18 Oct, 2010 1 commit
  33. 13 Aug, 2010 1 commit