1. 02 Mar, 2017 1 commit
  2. 14 Feb, 2017 1 commit
  3. 13 Feb, 2017 4 commits
  4. 19 Jan, 2017 1 commit
  5. 06 Oct, 2016 1 commit
    • alph's avatar
      [profiler] Tracing-based CPU profiler. · 4b575dfc
      alph authored
      A new V8 API object v8::TracingCpuProfiler is introduced.
      Client can create it on an isolate to enable JS CPU profiles collected
      during tracing session.
      
      Once the v8.cpu_profile2 tracing category is enabled the profiler emits
      CpuProfile and CpuProfileChunk events with the profile data.
      
      BUG=chromium:406277
      
      Review-Url: https://codereview.chromium.org/2396733002
      Cr-Commit-Position: refs/heads/master@{#40054}
      4b575dfc
  6. 29 Sep, 2016 1 commit
  7. 09 Sep, 2016 1 commit
  8. 10 Aug, 2016 1 commit
  9. 02 Aug, 2016 1 commit
  10. 08 Jul, 2016 1 commit
  11. 06 Jul, 2016 1 commit
    • lpy's avatar
      Expose TickSample and its APIs in v8-profiler.h · 3172f6a9
      lpy authored
      We want to eventually move the profiling functionality out of V8 as library,
      this patch exposes TickSample and its APIs in v8-profiler.h so that when
      embedders use library, they can have more details.
      
      Minor change: Rename tick-sample.[h|cc] to simulator-helper.[h|cc].
      
      BUG=v8:4789
      LOG=N
      
      Review-Url: https://codereview.chromium.org/2105943002
      Cr-Commit-Position: refs/heads/master@{#37564}
      3172f6a9
  12. 22 Jun, 2016 1 commit
  13. 04 May, 2016 1 commit
  14. 26 Jan, 2016 1 commit
  15. 22 Jan, 2016 1 commit
  16. 21 Jan, 2016 2 commits
  17. 03 Sep, 2015 1 commit
  18. 06 Jul, 2015 1 commit
  19. 03 Jun, 2015 1 commit
  20. 09 Apr, 2015 1 commit
    • thakis's avatar
      Fix C++ violation. · 1f7a7b32
      thakis authored
      gcc rejects the following snippet, clang rejects it in -std=c++11 mode:
        namespace A { template<class T> class C {}; }
        namespace B { template class A::C<int>; }
      
      Indeed, the C++ standard says in 14.7.2p2 "An explicit instantiation shall
      appear in an enclosing namespace of its template", so cl.exe is incorrect to
      allow this.
      
      Just move the instantiation out of the v8 namespace to fix.  No intended
      behavior change.  Fixes building with clang-cl on Windows.
      
      BUG=chromium:475643
      LOG=N
      TBR=svenpanne@chromium.org
      
      Review URL: https://codereview.chromium.org/1073903002
      
      Cr-Commit-Position: refs/heads/master@{#27721}
      1f7a7b32
  21. 08 Apr, 2015 1 commit
  22. 07 Apr, 2015 2 commits
  23. 26 Mar, 2015 1 commit
  24. 16 Mar, 2015 1 commit
  25. 10 Mar, 2015 2 commits
  26. 30 Jan, 2015 2 commits
  27. 06 Nov, 2014 1 commit
    • svenpanne@chromium.org's avatar
      The idea behind of this solution is to use the existing "relocation info"... · d56a21eb
      svenpanne@chromium.org authored
      The idea behind of this solution is to use the existing "relocation info" instead of consumption the CodeLinePosition events emitted by the V8 compilers.
      During generation code and relocation info are generated simultaneously.
      When code generation is done you each code object has associated "relocation info".
      Relocation information lets V8 to mark interesting places in the generated code: the pointers that might need to be relocated (after garbage collection),
      correspondences between the machine program counter and source locations for stack walking.
      
      This patch:
      1. Add more source positions info in reloc info to make it suitable for source level mapping.
      The amount of data should not be increased dramatically because (1) V8 already marks interesting places in the generated code and
      (2) V8 does not write redundant information (it writes a pair (pc_offset, pos) only if pos is changed and skips other).
      I measured it on Octane benchmark - for unoptimized code the number of source positions may achieve 2x ('lin_solve' from NavierStokes benchmark).
      
      2. When a sample happens, CPU profiler finds a code object by pc, then use its reloc info to match the sample to a source line.
      If a source line is found that hit counter is increased by one for this line.
      
      3. Add a new public V8 API to get the hit source lines by CDT CPU profiler.
      Note that it's expected a minor patch in Blink to pack the source level info in JSON to be shown.
      
      4.Add a test that checks how the samples are distributed through source lines.
      It tests two cases: (1) relocation info created during code generation and (2) relocation info associated with precompiled function's version.
      
      Patch from Denis Pravdin <denis.pravdin@intel.com>;
      
      R=svenpanne@chromium.org, yurys@chromium.org
      
      Review URL: https://codereview.chromium.org/682143003
      
      Patch from Weiliang <weiliang.lin@intel.com>.
      
      Cr-Commit-Position: refs/heads/master@{#25182}
      git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@25182 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      d56a21eb
  28. 02 Oct, 2014 2 commits
    • yurys@chromium.org's avatar
      Revert of Extend CPU profiler with mapping ticks to source lines (patchset #3... · 08c40baa
      yurys@chromium.org authored
      Revert of Extend CPU profiler with mapping ticks to source lines (patchset #3 id:40001 of https://codereview.chromium.org/616963005/)
      
      Reason for revert:
      It broke layout test fast/events/window-onerror-02.html, error column reported by window.onerror is now wrong (I believe it is because of the change in full-codegen):
      
      http://build.chromium.org/p/client.v8/builders/V8-Blink%20Linux%2064%20%28dbg%29/builds/652
      
      Original issue's description:
      > Extend CPU profiler with mapping ticks to source lines
      >
      > The idea behind of this solution is to use the existing "relocation info" instead of consumption the CodeLinePosition events emitted by the V8 compilers.
      > During generation code and relocation info are generated simultaneously.
      > When code generation is done you each code object has associated "relocation info".
      > Relocation information lets V8 to mark interesting places in the generated code: the pointers that might need to be relocated (after garbage collection),
      > correspondences between the machine program counter and source locations for stack walking.
      >
      > This patch:
      > 1. Add more source positions info in reloc info to make it suitable for source level mapping.
      > The amount of data should not be increased dramatically because (1) V8 already marks interesting places in the generated code and
      > (2) V8 does not write redundant information (it writes a pair (pc_offset, pos) only if pos is changed and skips other).
      > I measured it on Octane benchmark - for unoptimized code the number of source positions may achieve 2x ('lin_solve' from NavierStokes benchmark).
      >
      > 2. When a sample happens, CPU profiler finds a code object by pc, then use its reloc info to match the sample to a source line.
      > If a source line is found that hit counter is increased by one for this line.
      >
      > 3. Add a new public V8 API to get the hit source lines by CDT CPU profiler.
      > Note that it's expected a minor patch in Blink to pack the source level info in JSON to be shown.
      >
      > 4.Add a test that checks how the samples are distributed through source lines.
      > It tests two cases: (1) relocation info created during code generation and (2) relocation info associated with precompiled function's version.
      >
      > Patch from Denis Pravdin <denis.pravdin@intel.com>
      > BUG=None
      > LOG=Y
      > R=svenpanne@chromium.org
      >
      > Committed: https://code.google.com/p/v8/source/detail?r=24389
      
      TBR=svenpanne@chromium.org,danno@chromium.org,alph@chromium.org,denis.pravdin@intel.com,weiliang.lin@intel.com
      BUG=None
      LOG=N
      
      Review URL: https://codereview.chromium.org/624443005
      
      git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24394 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      08c40baa
    • yurys@chromium.org's avatar
      Extend CPU profiler with mapping ticks to source lines · 6482fb3e
      yurys@chromium.org authored
      The idea behind of this solution is to use the existing "relocation info" instead of consumption the CodeLinePosition events emitted by the V8 compilers.
      During generation code and relocation info are generated simultaneously.
      When code generation is done you each code object has associated "relocation info".
      Relocation information lets V8 to mark interesting places in the generated code: the pointers that might need to be relocated (after garbage collection),
      correspondences between the machine program counter and source locations for stack walking.
      
      This patch:
      1. Add more source positions info in reloc info to make it suitable for source level mapping.
      The amount of data should not be increased dramatically because (1) V8 already marks interesting places in the generated code and
      (2) V8 does not write redundant information (it writes a pair (pc_offset, pos) only if pos is changed and skips other).
      I measured it on Octane benchmark - for unoptimized code the number of source positions may achieve 2x ('lin_solve' from NavierStokes benchmark).
      
      2. When a sample happens, CPU profiler finds a code object by pc, then use its reloc info to match the sample to a source line.
      If a source line is found that hit counter is increased by one for this line.
      
      3. Add a new public V8 API to get the hit source lines by CDT CPU profiler.
      Note that it's expected a minor patch in Blink to pack the source level info in JSON to be shown.
      
      4.Add a test that checks how the samples are distributed through source lines.
      It tests two cases: (1) relocation info created during code generation and (2) relocation info associated with precompiled function's version.
      
      Patch from Denis Pravdin <denis.pravdin@intel.com>
      BUG=None
      LOG=Y
      R=svenpanne@chromium.org
      
      Review URL: https://codereview.chromium.org/616963005
      
      Patch from Denis Pravdin <denis.pravdin@intel.com>.
      
      git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24389 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      6482fb3e
  29. 22 May, 2014 1 commit
  30. 09 May, 2014 1 commit
  31. 29 Apr, 2014 1 commit
  32. 25 Apr, 2014 1 commit