1. 06 Jun, 2018 1 commit
  2. 05 Jun, 2018 2 commits
  3. 04 Jun, 2018 1 commit
  4. 31 May, 2018 1 commit
  5. 30 May, 2018 2 commits
  6. 29 May, 2018 1 commit
  7. 28 May, 2018 1 commit
  8. 24 May, 2018 2 commits
  9. 23 May, 2018 1 commit
    • Peter Marshall's avatar
      [cpu-profiler] Add a new profiling mode with a more detailed call tree. · ecae80cd
      Peter Marshall authored
      The current profiling mode (called kLeafNodeLineNumbers in this CL)
      produces a tree, with each node representing a stack frame that is seen
      in one or more samples taken during profiling. These nodes refer to a
      particular function in a stack trace, but not to a particular line or
      callsite within that function.
      
      This CL adds a new more (called kCallerLineNumbers) which produces a
      different profile tree, where each stack trace seen during profiling,
      including the line number, has a unique path in the tree.
      
      The profile tree was previously keyed on CodeEntry*. Now it is keyed on
      the pair of CodeEntry* and line_number, meaning it has distinct nodes
      for those combinations which exist, and each distinct stack trace that
      was sampled is represented in the tree.
      
      For optimized code where we have inline frames, there are no line
      numbers for the inline frames in the stack trace, causing duplicate
      branches in the tree with kNoLineNumberInfo as the reported line number.
      This will be addressed in follow-ups.
      
      Bug: v8:7018
      Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng
      Change-Id: I512e221508f5b50ec028306d212263b514a9fb24
      Reviewed-on: https://chromium-review.googlesource.com/1013493
      Commit-Queue: Peter Marshall <petermarshall@chromium.org>
      Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#53298}
      ecae80cd
  10. 17 May, 2018 2 commits
  11. 16 May, 2018 1 commit
  12. 14 May, 2018 1 commit
    • jgruber's avatar
      [api] Add a dedicated UnboundModuleScript type · 8ec92f51
      jgruber authored
      Module and script SharedFunctionInfos can't be used interchangeably
      (e.g.: it should not be possible to bind a Module's SFI to a Context).
      
      The dedicated type disambiguates the two.
      
      This also adds an overload for CreateCodeCache which takes an unbound
      module script instead of an unbound script. Both are just a SFI
      underneath, so their behavior is identical.
      
      Bug: v8:7685
      Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng
      Change-Id: Iab519d0d50b6b41c95abdb6397f5622e292da4d8
      Reviewed-on: https://chromium-review.googlesource.com/1047107
      Commit-Queue: Jakob Gruber <jgruber@chromium.org>
      Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
      Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#53150}
      8ec92f51
  13. 09 May, 2018 4 commits
  14. 08 May, 2018 1 commit
  15. 07 May, 2018 2 commits
  16. 04 May, 2018 2 commits
    • Erik Luo's avatar
      [debug] add ability to do side-effect-free call to NewInstance · 4b52f964
      Erik Luo authored
      Creating a new instance from a v8::Function will invoke its
      constructor. If it is an API callback that has not been marked as
      kHasNoSideEffect, this CL introduces a way to invoke it without
      throwing.
      
      Calls within the constructor are still checked for side effects.
      
      Bug: chromium:829571
      Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng
      Change-Id: Ia4e410d487e2847bc511cb96f0be30a3563991f6
      Reviewed-on: https://chromium-review.googlesource.com/1034116
      Commit-Queue: Erik Luo <luoe@chromium.org>
      Reviewed-by: 's avatarHannes Payer <hpayer@chromium.org>
      Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#53003}
      4b52f964
    • jgruber's avatar
      [api] Add Module::GetUnboundScript() · 2d3f6f91
      jgruber authored
      This method is intended for use by code caching as follows:
      
      1. The module is compiled (and perhaps instantiated).
      2. The embedder fetches and stores the module's unbound script (i.e.
         the shared function info).
      3. Module evaluation, maybe triggering lazy compilation.
      4. Generated code for the module (which hangs off the shared function
         info) is inserted into the code cache.
      
      Subsequent module loads can load from the code cache prior to
      evaluation.
      
      Bug: v8:7685
      Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng
      Change-Id: I80018cd921ab1a18323906a548b249e19d9f9509
      Reviewed-on: https://chromium-review.googlesource.com/1041745
      Commit-Queue: Jakob Gruber <jgruber@chromium.org>
      Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
      Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#52998}
      2d3f6f91
  17. 03 May, 2018 2 commits
  18. 30 Apr, 2018 2 commits
  19. 26 Apr, 2018 1 commit
  20. 25 Apr, 2018 2 commits
  21. 24 Apr, 2018 1 commit
  22. 23 Apr, 2018 1 commit
    • Andreas Haas's avatar
      [api] Split isolate allocation and initialization · 5c9b30ae
      Andreas Haas authored
      At the moment, the isolate is allocated and initialized in a single
      step. This has the downside that the platform cannot register the
      isolate before the isolate gets initialized, and therefore the platform
      is not available for the isolate during initialization. With this CL we
      register the uninitialized isolate on the platform and initialize the
      isolate after that.
      
      This change is needed to allow the creation of task runners already
      during the initialization of the isolate.
      
      The related chromium CL: https://crrev.com/c/1015020
      
      R=yangguo@chromium.org
      
      Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng
      Change-Id: I52e89388a757f2693d1a800e7aa7701aa0080795
      Reviewed-on: https://chromium-review.googlesource.com/1014044Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Commit-Queue: Andreas Haas <ahaas@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#52731}
      5c9b30ae
  23. 19 Apr, 2018 1 commit
  24. 17 Apr, 2018 3 commits
  25. 16 Apr, 2018 1 commit
  26. 13 Apr, 2018 1 commit