1. 27 Mar, 2018 1 commit
  2. 22 Mar, 2018 3 commits
  3. 20 Mar, 2018 2 commits
  4. 16 Mar, 2018 1 commit
  5. 25 Jan, 2018 1 commit
    • Yang Guo's avatar
      Introduce SimpleNumberDictionary. · 3857b44e
      Yang Guo authored
      This is somewhat of a revival of what used to be
      UnseededNumberDictionary. The difference to NumberDictionary is that
      each entry only has two fields (no field for property details) and there
      is no header field for a bitfield.
      
      The reason for this change is memory regression introduced when we
      removed UnseededNumberDictionary (6e1c57ea). We now use
      SimpleNumberDictionary for
      - slow template instantiation cache
      - code stubs table
      - value serializer map
      - stack frame cache
      - type profile source positions
      
      R=ishell@chromium.org, ulan@chromium.org
      
      Bug: chromium:783695
      Change-Id: I3cd32e485060bb379fb2279eeefbbbded7455f0e
      Reviewed-on: https://chromium-review.googlesource.com/885811Reviewed-by: 's avatarIgor Sheludko <ishell@chromium.org>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Commit-Queue: Yang Guo <yangguo@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#50869}
      3857b44e
  6. 07 Dec, 2017 1 commit
  7. 22 Nov, 2017 1 commit
  8. 17 Nov, 2017 1 commit
    • Ulan Degenbaev's avatar
      [runtime] Make layout descriptor helper safe for concurrent marking. · 61bf2cc6
      Ulan Degenbaev authored
      The layout descriptor helper computes the object header size using
      map->instance_size() and map->GetInObjectProperties().
      
      It races with finalization of slack tracking, which changes both
      the instance size and the in-object properties count.
      
      This patch replaces the in-object properties count byte in the map
      with the byte that stores the start offset of in-object properties.
      
      The new byte can be used in the layout descriptor to compute the
      object header size and it is immutable.
      
      This patch also renames InstanceSize to InstanceSizeInWords where
      the instance size is represented in words.
      
      Bug: chromium:786069, chromium:694255
      Change-Id: I4b48c6944d3fe8a950bd7b0ba43d75216b177a78
      Reviewed-on: https://chromium-review.googlesource.com/776720
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarIgor Sheludko <ishell@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49461}
      61bf2cc6
  9. 14 Nov, 2017 1 commit
  10. 07 Nov, 2017 1 commit
  11. 15 Sep, 2017 1 commit
  12. 03 Sep, 2017 1 commit
  13. 10 Jul, 2017 1 commit
  14. 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
  15. 09 Jun, 2017 1 commit
  16. 17 May, 2017 1 commit
  17. 15 May, 2017 2 commits
  18. 26 Apr, 2017 1 commit
  19. 25 Apr, 2017 1 commit
  20. 09 Feb, 2017 1 commit
  21. 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
  22. 16 Jan, 2017 2 commits
  23. 21 Nov, 2016 1 commit
  24. 29 Aug, 2016 1 commit
  25. 29 Jun, 2016 1 commit
  26. 10 Jun, 2016 1 commit
  27. 27 Apr, 2016 1 commit
  28. 11 Mar, 2016 1 commit
  29. 22 Feb, 2016 1 commit
  30. 22 Dec, 2015 1 commit
  31. 30 Nov, 2015 1 commit
  32. 12 Nov, 2015 2 commits
  33. 11 Nov, 2015 1 commit
  34. 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