1. 15 Sep, 2017 1 commit
  2. 03 Sep, 2017 1 commit
  3. 10 Jul, 2017 1 commit
  4. 30 Jun, 2017 1 commit
    • Mathias Bynens's avatar
      [elements] Rename FAST elements kinds · 26c00f4a
      Mathias Bynens authored
      The `FAST_` prefix doesn’t make much sense — they’re all just different cases
      with their own optimizations. Packedness being implicit (e.g. `FAST_ELEMENTS`
      vs. `FAST_HOLEY_ELEMENTS`) is not ideal, either.
      
      This patch renames the FAST elements kinds as follows:
      
      - e.g. FAST_ELEMENTS => PACKED_ELEMENTS
      - e.g. FAST_HOLEY_ELEMENTS => HOLEY_ELEMENTS
      
      The following exceptions are left intact, for lack of a better name:
      
      - FAST_SLOPPY_ARGUMENTS_ELEMENTS
      - SLOW_SLOPPY_ARGUMENTS_ELEMENTS
      - FAST_STRING_WRAPPER_ELEMENTS
      - SLOW_STRING_WRAPPER_ELEMENTS
      
      This makes it easier to reason about elements kinds, and less confusing to
      explain how they’re used.
      
      R=jkummerow@chromium.org, cbruni@chromium.org
      BUG=v8:6548
      
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: Ie7c6bee85583c3d84b730f7aebbd70c1efa38af9
      Reviewed-on: https://chromium-review.googlesource.com/556032Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Reviewed-by: 's avatarCamillo Bruni <cbruni@chromium.org>
      Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
      Commit-Queue: Mathias Bynens <mathias@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#46361}
      26c00f4a
  5. 09 Jun, 2017 1 commit
  6. 17 May, 2017 1 commit
  7. 15 May, 2017 2 commits
  8. 26 Apr, 2017 1 commit
  9. 25 Apr, 2017 1 commit
  10. 09 Feb, 2017 1 commit
  11. 27 Jan, 2017 1 commit
    • julien.gilli's avatar
      add post-mortem metadata for frames type · cd96c7cc
      julien.gilli authored
      Previously (and still currently for some of them), post-mortem debugging
      tools were using StandardFrameConstants::kContextOffset as the offset to
      get the value that represents a frame's type.
      
      However since https://codereview.chromium.org/1696043002, a new, more
      general offset was introduced:
      CommonFrameConstants::kContextOrFrameTypeOffset.
      
      In order for post-mortem debugging tools to use this constant, it is
      included in the generated post-mortem metadata.
      
      R=danno@chromium.org,bmeurer@chromium.org
      BUG=
      
      Review-Url: https://codereview.chromium.org/2655553006
      Cr-Commit-Position: refs/heads/master@{#42746}
      cd96c7cc
  12. 16 Jan, 2017 2 commits
  13. 21 Nov, 2016 1 commit
  14. 29 Aug, 2016 1 commit
  15. 29 Jun, 2016 1 commit
  16. 10 Jun, 2016 1 commit
  17. 27 Apr, 2016 1 commit
  18. 11 Mar, 2016 1 commit
  19. 22 Feb, 2016 1 commit
  20. 22 Dec, 2015 1 commit
  21. 30 Nov, 2015 1 commit
  22. 12 Nov, 2015 2 commits
  23. 11 Nov, 2015 1 commit
  24. 25 Sep, 2015 1 commit
    • julien.gilli's avatar
      Update post-mortem metadata generation · 56a0a797
      julien.gilli authored
      mdb_v8, a post-mortem debugger for Node.js, now uses JSArrayBuffer's
      backing_store property and JSArrayBufferView's byte_offset property to
      get access to the content of Buffer instances in node (which are
      Uint8Array instances). This change adds post-mortem metadata for these
      two properties.
      
      This change also fixes a typo in
      inobject_properties_of_constructor_function_index_offset that was added
      to gen-postmortem-metadata in a previous change. It should be named
      inobject_properties_or_constructor_function_index instead.
      
      R=bmeurer@chromium.org
      
      Review URL: https://codereview.chromium.org/1363403003
      
      Cr-Commit-Position: refs/heads/master@{#30926}
      56a0a797
  25. 23 Sep, 2015 1 commit
  26. 21 Sep, 2015 1 commit
    • julien.gilli's avatar
      Add ScopeInfo constants to post-mortem metadata · 357e6b99
      julien.gilli authored
      mdb_v8, a post-mortem debugging tool for Node.js, allows users to
      inspect ScopeInfo structures in order to get more information about
      closures.
      
      Currently, it hardcodes the metadata it uses to find this information.
      This change allows it to get this metadata from the node binary itself,
      and thus to adapt to future changes made to the layout of the ScopeInfo
      data structure.
      
      BUG=
      
      R=bmeurer@chromium.org
      
      Review URL: https://codereview.chromium.org/1350843003
      
      Cr-Commit-Position: refs/heads/master@{#30843}
      357e6b99
  27. 18 Sep, 2015 1 commit
  28. 02 Sep, 2015 1 commit
  29. 25 Mar, 2015 1 commit
  30. 02 Feb, 2015 1 commit
  31. 10 Sep, 2014 1 commit
  32. 23 Jul, 2014 1 commit
  33. 02 Apr, 2014 1 commit
  34. 30 Dec, 2013 1 commit
  35. 14 Oct, 2013 1 commit
  36. 03 Jan, 2013 1 commit
  37. 28 Dec, 2012 1 commit