1. 22 May, 2019 1 commit
  2. 21 May, 2019 7 commits
  3. 20 May, 2019 3 commits
  4. 17 May, 2019 4 commits
  5. 16 May, 2019 4 commits
  6. 15 May, 2019 5 commits
  7. 14 May, 2019 5 commits
  8. 13 May, 2019 3 commits
  9. 10 May, 2019 2 commits
  10. 09 May, 2019 2 commits
  11. 08 May, 2019 3 commits
    • Maciej Goszczycki's avatar
      Reland "[heap] Set read-only space's and its pages' heap_ to null." · b672d089
      Maciej Goszczycki authored
      Seems like the CodeBuilder CL actually caused this.
      
      This is a reland of 964edc25
      
      Original change's description:
      > [heap] Set read-only space's and its pages' heap_ to null.
      >
      > Various small changes are required to enable this.
      >
      > HeapObject::GetReadOnlyRoots no longer uses the Space's heap when
      > possible (see comment in ReadOnlyHeap::GetReadOnlyRoots definition).
      > This requires that ReadOnlyRoots be construct-able using a raw pointer
      > to the read-only space's roots array.
      >
      > Global read-only heap state is now cleared by tests where appropriate
      > and extra DCHECKs in ReadOnlyHeap::SetUp should make catching future
      > issues easier.
      >
      > String padding is now always cleared just before read-only space is
      > sealed when not deserializing.
      >
      > Change-Id: I7d1db1c11567be5df06ff7066f3a699125f8b372
      > Bug: v8:7464
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1535830
      > Commit-Queue: Maciej Goszczycki <goszczycki@google.com>
      > Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
      > Reviewed-by: Dan Elphick <delphick@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#61188}
      
      Bug: v8:7464
      Change-Id: If75bbd16c2e2af5b80cd60811dfd7866f8be8309
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1599186
      Commit-Queue: Maciej Goszczycki <goszczycki@google.com>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarDan Elphick <delphick@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61323}
      b672d089
    • Peter Marshall's avatar
      [tracing] Implement RunsTasksOnCurrentThread for the worker task runner · 78e2f3ff
      Peter Marshall authored
      This is needed for Perfetto which sometimes chooses to bypass the task
      queue if the task queue uses a given thread to run tasks.
      
      Bug: v8:8339
      Change-Id: Iecec5e7883d174e4b63495ecdadfb96105e4505c
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1588471
      Commit-Queue: Peter Marshall <petermarshall@chromium.org>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Auto-Submit: Peter Marshall <petermarshall@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61316}
      78e2f3ff
    • Simon Zünd's avatar
      Reland "[torque] Introduce force_assert_statements compiler option" · 2e3862d7
      Simon Zünd authored
      This is a reland of 2d45ecf0
      
      The reland properly initializes struct fields in unittests. To prevent
      this in the future, TorqueCompilerOptions uses brace initialization.
      
      Original change's description:
      > [torque] Introduce force_assert_statements compiler option
      >
      > "assert(...)" statements are usually only visited and generated in
      > debug builds. To provide Language Server support for statements inside
      > asserts, the force_assert_statements option allows to manually
      > override this behavior and visit assert statements in release builds.
      >
      > R=sigurds@chromium.org
      >
      > Bug: v8:7793
      > Change-Id: I38f48e35f2b0a1a98abb74b7babb1edd2d7dba24
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1599180
      > Auto-Submit: Simon Zünd <szuend@chromium.org>
      > Commit-Queue: Sigurd Schneider <sigurds@chromium.org>
      > Reviewed-by: Sigurd Schneider <sigurds@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#61295}
      
      Bug: v8:7793
      Change-Id: I96ef863c8c85ae87a00cbe858655d4a2c9368b41
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1599599
      Auto-Submit: Simon Zünd <szuend@chromium.org>
      Reviewed-by: 's avatarSigurd Schneider <sigurds@chromium.org>
      Commit-Queue: Sigurd Schneider <sigurds@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61315}
      2e3862d7
  12. 07 May, 2019 1 commit
    • Simon Zünd's avatar
      [torque-ls] Add boilerplate for DocumentSymbol requests and responses · 034defad
      Simon Zünd authored
      DocumentSymbol responses provide all symbols (macros, classes, etc.)
      in a given document. The LSP standard evolved over time and supports
      two different kind of responses here:
        - A simpler one, that is a plain list of all the symbols
        - A more detailed one, allowing a hierarchy of symbols. For example
          a class symbol has a list of field/method symbols attached. This
          is used by editors to build hierarchical outline views.
      
      For now, the simpler response is chosen as its also used for
      workspace wide symbol searches.
      
      This CL adds the necessary boilerplate so the actual implementation CL
      is easier to review.
      
      R=tebbi@chromium.org
      
      Bug: v8:8880
      Change-Id: I6c86fc839b1f4e0309f6403a5f9afd5c162c0e89
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1598757
      Auto-Submit: Simon Zünd <szuend@chromium.org>
      Commit-Queue: Tobias Tebbi <tebbi@chromium.org>
      Reviewed-by: 's avatarTobias Tebbi <tebbi@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61294}
      034defad