1. 11 Aug, 2020 1 commit
  2. 27 Nov, 2019 1 commit
  3. 25 Nov, 2019 2 commits
    • Dan Elphick's avatar
      Delete redundant code in OptimizingCompileDispatcher::Stop · ead247c1
      Dan Elphick authored
      Removes job queue flushing in OptimizingCompileDispatcher::Stop when
      FLAG_concurrent_recompilation_delay is set. Before this explicit
      flushing was run, there was already a wait-loop which ensured the queue
      was always empty.
      
      Bug: v8:9810
      Change-Id: I620bac9c9d73aead671b178c9450bdd25e6761b1
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1934332
      Commit-Queue: Dan Elphick <delphick@chromium.org>
      Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
      Auto-Submit: Dan Elphick <delphick@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#65154}
      ead247c1
    • Mythri A's avatar
      [TurboFan] Add RuntimeStats counters for main thread TurboFan phases · 84b35324
      Mythri A authored
      Adds RuntimeStats counters for HeapBrokerInitialization, Serialize,
      SerializeMetadata and Finalization phases. These happen only on main thread.
      In a followup cl we will also add counters for other phases that could happen
      on main thread or background thread.
      
      Earlier RecompileSynchronous was used to measure the time spent in Concurrent,
      non Concurrent and Concurrent finalize phases. This cl replaces them with
      OptimizeConcurrent, OptimizeNonConcurrent and OptimizeConcurrentFinalize
      counters. This cl also renames RecompileConcurrent to OptimizeBackground to
      make it clear this measures the background component of optimization.
      
      This also updates names of trace events to be in-sync with RuntimeStat counters.
      
      Bug: v8:9684
      Change-Id: Ifda81ce7ab1c659c2df53bab924c51c46f46939b
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1924439Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Reviewed-by: 's avatarDan Elphick <delphick@chromium.org>
      Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
      Commit-Queue: Mythri Alle <mythria@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#65147}
      84b35324
  4. 10 Sep, 2019 1 commit
  5. 24 May, 2019 1 commit
  6. 23 May, 2019 2 commits
  7. 22 May, 2019 1 commit
  8. 21 May, 2019 1 commit
  9. 20 May, 2019 1 commit
  10. 17 May, 2019 2 commits
  11. 26 Feb, 2019 1 commit
  12. 22 Jan, 2019 1 commit
  13. 13 Nov, 2018 1 commit
  14. 09 Nov, 2018 1 commit
  15. 12 Oct, 2018 1 commit
  16. 25 Sep, 2018 1 commit
  17. 17 Sep, 2018 1 commit
  18. 14 Sep, 2018 1 commit
  19. 07 Sep, 2018 1 commit
  20. 23 Jun, 2018 1 commit
  21. 04 Apr, 2018 1 commit
  22. 26 Mar, 2018 1 commit
  23. 22 Mar, 2018 3 commits
  24. 20 Mar, 2018 2 commits
  25. 01 Mar, 2018 1 commit
    • Gabriel Charette's avatar
      [v8 platform] Get rid of unused ExpectedRuntime parameter. · 86b4b534
      Gabriel Charette authored
      With a temporary intermediate step to allow adapting embedders before
      getting rid of the ExpectedRuntime method altogether.
      
      The method is being renamed to CallOnWorkerThread() as an effort to
      go away from "background" nomenclature for worker threads ("background"
      usually refers to a priority but worker threads are commonly used for
      high priority tasks in v8).
      Other CLs will follow to rename other "background" APIs.
      
      Bug: v8:7310
      Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng;master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: I2fd4eac7458708d4eacb0f4871c982a567a3865e
      Reviewed-on: https://chromium-review.googlesource.com/941442
      Commit-Queue: Gabriel Charette <gab@chromium.org>
      Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#51645}
      86b4b534
  26. 22 Feb, 2018 1 commit
    • Benedikt Meurer's avatar
      [cleanup] Introduce a dedicated FeedbackCell. · aff1f378
      Benedikt Meurer authored
      This is preparatory cleanup work for eventually tracking the functions
      (rather than concrete closures) in the CALL_IC, also for builtins like
      the default PromiseCapability [[Resolve]] and [[Reject]] functions. It
      adds a new FeedbackCell type, which is used by JSFunctions consistently
      now to reference the feedback vector (or undefined if not the function
      is not compiled yet or is a native/asm.js function).
      
      This also changes the calling convention for FastNewClosure builtin and
      the JSCreateClosure operator in TurboFan to carry the FeedbackCell here
      instead of the parent FeedbackVector and the slot index. In addition we
      eliminate the now unused %InterpreterNewClosure runtime function.
      
      Bug: v8:2206, v8:7253, v8:7310
      Change-Id: Ib4ce456e276e0273e57c163dcdd0b33abf863656
      Reviewed-on: https://chromium-review.googlesource.com/928403
      Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
      Reviewed-by: 's avatarMichael Stanton <mvstanton@chromium.org>
      Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#51474}
      aff1f378
  27. 16 Nov, 2017 1 commit
  28. 15 Nov, 2017 1 commit
  29. 13 Oct, 2017 1 commit
  30. 28 Sep, 2017 1 commit
  31. 11 Aug, 2017 1 commit
  32. 03 Aug, 2017 1 commit
  33. 19 Jun, 2017 1 commit
    • Leszek Swirski's avatar
      [compiler] Drive optimizations with feedback vector (reland) · 24b7026d
      Leszek Swirski authored
      For interpreted functions, use the optimized code slot in the feedback
      vector to store an optimization marker (optimize/in optimization queue)
      rather than changing the JSFunction's code object. Then, adapt the
      self-healing mechanism to also dispatch based on this optimization
      marker. Similarly, replace SFI marking with optimization marker checks
      in CompileLazy.
      
      This allows JSFunctions to share optimization information (replacing
      shared function marking) without leaking this information across native
      contexts. Non I+TF functions (asm.js or --no-turbo) use a
      CheckOptimizationMarker shim which generalises the old
      CompileOptimized/InOptimizationQueue builtins and also checks the same
      optimization marker as CompileLazy and InterpreterEntryTrampoline.
      
      This is a reland of https://chromium-review.googlesource.com/c/509716
      
      Change-Id: I02b790544596562373da4c9c9f6afde5fb3bcffe
      Reviewed-on: https://chromium-review.googlesource.com/535460Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45997}
      24b7026d
  34. 13 Jun, 2017 1 commit
    • Leszek Swirski's avatar
      Revert "[compiler] Drive optimizations with feedback vector" · 58978da6
      Leszek Swirski authored
      This reverts commit e39c9e02.
      
      Reason for revert: Breaks https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20debug/builds/15561
      
      Original change's description:
      > [compiler] Drive optimizations with feedback vector
      > 
      > For interpreted functions, use the optimized code slot in the feedback vector
      > to store an optimization marker (optimize/in optimization queue) rather than
      > changing the JSFunction's code object. Then, adapt the self-healing mechanism
      > to also dispatch based on this optimization marker. Similarly, replace SFI
      > marking with optimization marker checks in CompileLazy.
      > 
      > This allows JSFunctions to share optimization information (replacing shared
      > function marking) without leaking this information across native contexts. Non
      > I+TF functions (asm.js or --no-turbo) use a CheckOptimizationMarker shim which
      > generalises the old CompileOptimized/InOptimizationQueue builtins and also
      > checks the same optimization marker as CompileLazy and
      > InterpreterEntryTrampoline.
      > 
      > Change-Id: I6826bdde7ab9a919cdb6b69bc0ebc6174bcb91ae
      > Reviewed-on: https://chromium-review.googlesource.com/509716
      > Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#45901}
      
      TBR=rmcilroy@chromium.org,mstarzinger@chromium.org,leszeks@chromium.org
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      
      Change-Id: Ib6c2b4d90fc5f659a6dcaf3fd30321507ca9cb94
      Reviewed-on: https://chromium-review.googlesource.com/532916Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
      Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45903}
      58978da6