1. 30 Sep, 2021 1 commit
  2. 07 Jun, 2021 1 commit
  3. 14 May, 2021 1 commit
  4. 20 Apr, 2021 1 commit
  5. 08 Apr, 2021 2 commits
  6. 09 Oct, 2020 1 commit
  7. 01 Oct, 2020 1 commit
    • Dan Elphick's avatar
      [CSA] Tnodify CodeAssembler::Parameter · 74a9b9c4
      Dan Elphick authored
      CodeAssembler::Parameter now takes a Type template parameter and
      performs a checked cast to it. There is also UncheckedParameter which
      returns a TNode but doesn't check the cast. The original Parameter
      method is still there as UntypedParameter.
      
      Parameter<T>(x) in many cases replaces CAST(Parameter(x)), where the
      cast is performed inside Parameter. Since Parameter is not a macro,
      this means it cannot see the original expression or its file name and
      line number. So the error messages are vaguely useful, Parameter<T>()
      takes a SourceLocation parameter which with a default value of
      SourceLocation::Current(), which at least gives us the file name and
      line number for the error message.
      
      Bug: v8:6949, v8:10933
      Change-Id: I27157bec7dc7462210c1eb9c430c0180217d25c1
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2435106Reviewed-by: 's avatarBill Budge <bbudge@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Reviewed-by: 's avatarSantiago Aboy Solanes <solanes@chromium.org>
      Commit-Queue: Dan Elphick <delphick@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70264}
      74a9b9c4
  8. 29 Sep, 2020 1 commit
  9. 05 Jun, 2020 1 commit
  10. 06 May, 2020 1 commit
    • Gus Caplan's avatar
      [API] Fix microtask message reporting · 767e65f9
      Gus Caplan authored
      RunSingleMicrotask calls Runtime::ReportMessage, but the implementation
      of ReportMessage would unconditionally discard these exceptions. This
      CL removes all of the intermediate logic and directly calls
      MessageHandler::ReportMessage, restoring the ability of
      RunSingleMicrotask to report exceptions that occur in microtasks.
      
      Bug: v8:8326
      Change-Id: I493de74383b2ab191d786611fb9eba9d27e7a243
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2162121
      Commit-Queue: Gus Caplan <me@gus.host>
      Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#67630}
      767e65f9
  11. 05 May, 2020 1 commit
  12. 26 Mar, 2020 1 commit
  13. 06 Mar, 2020 1 commit
  14. 19 Feb, 2020 1 commit
  15. 18 Feb, 2020 1 commit
  16. 14 Feb, 2020 1 commit
  17. 15 Jan, 2020 1 commit
  18. 30 Oct, 2019 1 commit
  19. 21 Oct, 2019 1 commit
  20. 18 Sep, 2019 1 commit
  21. 12 Sep, 2019 1 commit
  22. 04 Sep, 2019 1 commit
  23. 27 Aug, 2019 1 commit
  24. 26 Aug, 2019 1 commit
  25. 30 Jul, 2019 1 commit
    • Sathya Gunasekaran's avatar
      [WeakRefs] Make cleanup callback run as a task · 743ce772
      Sathya Gunasekaran authored
      Previously, this was run as a microtask and this CL changes it to run
      as a separate task as mandated by the current WeakRef spec.
      
      This CL also introduces a FinalizationGroup type to the V8 API
      representing the JSFinalizationGroup. This has a `Cleanup`
      function that runs the cleanup callback associated with it.
      
      SetHostCleanupFinalizationGroupCallback is added to set
      the embedder defined HostCleanupFinalizationGroupCallback.
      
      ClearKeptObject is exposed on the v8::Isolate to reset the strongly
      held set of objects.
      
      The general workflow is the following:
      
      (a) When the GC notices that a given finalization group has dirty
          cells, it calls HostCleanupFinalizationGroupCallback with the given
          finalization group.
      
      (b) As part of HostCleanupFinalizationGroupCallback, the embedder
          enqueues a task that at some point later calls
          FinalizationGroup::Cleanup.
      
      (c) At some point in the future, FinalizationGroup::Cleanup is called,
          which runs the cleanup callback of the finalization group.
      
      This patch also includes d8 changes to use these new APIs. Currently,
      d8 cycles through the enqueued finalization groups after a synchronous
      turn (and it's microtask checkpoint) and runs the cleanup callbacks.
      
      Change-Id: I06eb4da2c103b2792a9c62bc4b98fd4e5c4892fc
      Bug: v8:8179
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1655655
      Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarHannes Payer <hpayer@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#62984}
      743ce772
  26. 22 May, 2019 1 commit
  27. 21 May, 2019 1 commit
  28. 17 May, 2019 1 commit
  29. 16 May, 2019 2 commits
  30. 09 Apr, 2019 1 commit
  31. 27 Feb, 2019 1 commit
    • tzik's avatar
      Reland "Do not enqueue or run a microtask on detached contexts" · a32e37ed
      tzik authored
      This is a reland of 734a6575
      
      Original change's description:
      > Do not enqueue or run a microtask on detached contexts
      >
      > This CL disables EnqueueMicrotask and RunMicrotasks on detached
      > contexts. That is, if an embedder call DetachGlobal() on a v8::Context,
      > EnqueueMicrotask on that context will not take effect, and all Microtask
      > that is enqueued before DetachGlobal will be cancelled.
      >
      > On Blink, this implies that a frame will no longer run a microtask after
      > it's navigated away. OTOH, detached frames in Blink are not affected.
      >
      > Bug: v8:8124
      > Change-Id: I5b00ceef5ea2afb87cf067a65eb95c29bf91176d
      > Reviewed-on: https://chromium-review.googlesource.com/c/1416071
      > Reviewed-by: Toon Verwaest <verwaest@chromium.org>
      > Reviewed-by: Yang Guo <yangguo@chromium.org>
      > Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
      > Reviewed-by: Adam Klein <adamk@chromium.org>
      > Commit-Queue: Taiju Tsuiki <tzik@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#59445}
      
      Tbr: adamk@chromium.org, yangguo@chromium.org, verwaest@chromium.org
      Bug: v8:8124
      Change-Id: I959a18ae214f1385d5f453b3ed94772e60f71e0f
      Reviewed-on: https://chromium-review.googlesource.com/c/1469544
      Commit-Queue: Taiju Tsuiki <tzik@chromium.org>
      Reviewed-by: 's avatarBenedikt Meurer <bmeurer@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#59884}
      a32e37ed
  32. 21 Feb, 2019 2 commits
  33. 15 Feb, 2019 1 commit
  34. 08 Feb, 2019 3 commits
  35. 30 Jan, 2019 1 commit