1. 11 Jun, 2018 1 commit
    • Matheus Marchini's avatar
      [log] fix ExistingCodeLogger behavior on edge case · b20faffb
      Matheus Marchini authored
      ExistingCodeLogger was behaving incorrectly when the CodeEventHandler
      API was used in combination with --interpreted-frames-native-stack.
      Instead of collecting copied trampolines as InterpretedFunction:functionName,
      they were being collected as Builtin:IntepreterEntryTrampolines.
      This patch adds special handling for copied trampolines when
      using ExistingCodeLogger.
      
      R=yangguo@google.com
      
      Change-Id: I3ee4be03800122d28d53b51b20c60dcf6263e4c1
      Reviewed-on: https://chromium-review.googlesource.com/1087813Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Commit-Queue: Yang Guo <yangguo@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#53624}
      b20faffb
  2. 28 May, 2018 1 commit
  3. 15 May, 2018 1 commit
  4. 04 May, 2018 1 commit
  5. 02 May, 2018 1 commit
  6. 18 Apr, 2018 1 commit
  7. 17 Apr, 2018 2 commits
  8. 14 Apr, 2018 1 commit
    • Jakob Kummerow's avatar
      [ubsan] Change Address typedef to uintptr_t · 2459046c
      Jakob Kummerow authored
      The "Address" type is V8's general-purpose type for manipulating memory
      addresses. Per the C++ spec, pointer arithmetic and pointer comparisons
      are undefined behavior except within the same array; since we generally
      don't operate within a C++ array, our general-purpose type shouldn't be
      a pointer type.
      
      Bug: v8:3770
      Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel
      Change-Id: Ib96016c24a0f18bcdba916dabd83e3f24a1b5779
      Reviewed-on: https://chromium-review.googlesource.com/988657
      Commit-Queue: Jakob Kummerow <jkummerow@chromium.org>
      Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#52601}
      2459046c
  9. 06 Apr, 2018 1 commit
  10. 05 Apr, 2018 1 commit
    • jgruber's avatar
      Rename Code::instruction_{start,end,size} functions · 7b29fe43
      jgruber authored
      In order to clarify the difference between, e.g., InstructionStart and
      instruction_start, rename as follows:
      
      Code::instruction_start -> raw_instruction_start
      Code::instruction_end   -> raw_instruction_end
      Code::instruction_size  -> raw_instruction_size
      
      The difference between the camel-case and raw_* function families is
      in how they handle off-heap-trampoline Code objects. For example, when
      called on an off-heap-trampoline: raw_instruction_start returns the
      trampoline's entry point, while InstructionStart returns the off-heap
      code's entry point (located in the .text section of the binary).
      
      Some callsites were updated to call the camel-case function family as
      appropriate.
      
      Bug: v8:6666
      Change-Id: I4a572f47c2d161a853599d7c17879e263b0d1a87
      Reviewed-on: https://chromium-review.googlesource.com/997532
      Commit-Queue: Jakob Gruber <jgruber@chromium.org>
      Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#52387}
      7b29fe43
  11. 23 Mar, 2018 2 commits
  12. 22 Mar, 2018 4 commits
  13. 21 Mar, 2018 1 commit
  14. 20 Mar, 2018 2 commits
  15. 16 Mar, 2018 1 commit
  16. 09 Mar, 2018 1 commit
  17. 05 Mar, 2018 1 commit
  18. 26 Feb, 2018 1 commit
  19. 20 Feb, 2018 1 commit
  20. 05 Feb, 2018 1 commit
  21. 20 Dec, 2017 2 commits
  22. 08 Dec, 2017 1 commit
  23. 05 Dec, 2017 1 commit
  24. 29 Nov, 2017 1 commit
  25. 22 Nov, 2017 1 commit
  26. 17 Nov, 2017 2 commits
  27. 14 Nov, 2017 2 commits
    • Jakob Gruber's avatar
      Revert "Revert lazy bytecode handler support" · e0400694
      Jakob Gruber authored
      This reverts commit 9e4543a2.
      
      Reason for revert: Culprit CL was found, let's reland this.
      
      Original change's description:
      > Revert lazy bytecode handler support
      >
      > Speculative revert due to canary crashes. I'll begin relanding these
      > one-by-one next week.
      >
      > This bundles two reverts:
      >
      > Revert "[snapshot] Lazy-deserialize bytecode handlers"
      > This reverts commit b4587369.
      >
      > Revert "[interpreter] Remove mechanism for bytecode handler reuse"
      > This reverts commit 07fc87a2.
      >
      > TBR: rmcilroy@chromium.org,mlippautz@chromium.org,yangguo@chromium.org
      > Bug: chromium:783708
      > Change-Id: I6f8314b9eeafd9412a1c69843bc242e7da240eee
      > Reviewed-on: https://chromium-review.googlesource.com/763428
      > Commit-Queue: Jakob Gruber <jgruber@chromium.org>
      > Reviewed-by: Jakob Gruber <jgruber@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#49294}
      
      TBR=rmcilroy@chromium.org,mlippautz@chromium.org,yangguo@chromium.org
      
      # Not skipping CQ checks because original CL landed > 1 day ago.
      
      Bug: chromium:783708
      Change-Id: I6c9274ddf0d0832ecce32baacc4f6a1388f56ac4
      Reviewed-on: https://chromium-review.googlesource.com/768749
      Commit-Queue: Jakob Gruber <jgruber@chromium.org>
      Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49362}
      e0400694
    • Camillo Bruni's avatar
      [log] Support --log-function-events in the parser · e634740b
      Camillo Bruni authored
      This partially retires --trace-parse and --trace-preparse which will be fully removed in
      a later CL.
      
      Drive-by-fix: make the Parser constructor arguments order more
      consistent.
      
      Bug: chromium:757467
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: I80a688ce553adfa65ad346718604bd53a9e606a9
      Reviewed-on: https://chromium-review.googlesource.com/744046
      Commit-Queue: Camillo Bruni <cbruni@chromium.org>
      Reviewed-by: 's avatarMarja Hölttä <marja@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49350}
      e634740b
  28. 10 Nov, 2017 1 commit
    • jgruber's avatar
      Revert lazy bytecode handler support · 9e4543a2
      jgruber authored
      Speculative revert due to canary crashes. I'll begin relanding these
      one-by-one next week.
      
      This bundles two reverts:
      
      Revert "[snapshot] Lazy-deserialize bytecode handlers"
      This reverts commit b4587369.
      
      Revert "[interpreter] Remove mechanism for bytecode handler reuse"
      This reverts commit 07fc87a2.
      
      TBR: rmcilroy@chromium.org,mlippautz@chromium.org,yangguo@chromium.org
      Bug: chromium:783708
      Change-Id: I6f8314b9eeafd9412a1c69843bc242e7da240eee
      Reviewed-on: https://chromium-review.googlesource.com/763428
      Commit-Queue: Jakob Gruber <jgruber@chromium.org>
      Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49294}
      9e4543a2
  29. 08 Nov, 2017 1 commit
  30. 07 Nov, 2017 2 commits