1. 23 Jul, 2018 1 commit
  2. 18 Jul, 2018 1 commit
  3. 23 Jun, 2018 1 commit
  4. 18 Jun, 2018 1 commit
    • Clemens Hammacher's avatar
      Make CallInterfaceDescriptor isolate-independent · 3cb376dc
      Clemens Hammacher authored
      Currently each isolate stores its own array of
      {CallInterfaceDescriptorData}. This array has size 173, and each entry
      has 40 bytes. That's already 7kB per isolate.
      Additionally, each {CallInterfaceDescriptorData} allocates two
      heap-allocated arrays, which probably add up to more than the static
      size of the {CallInterfaceDescriptorData}. Note that all the
      {CallInterfaceDescriptorData} instances are initialized eagerly on
      isolate creation.
      
      Since {CallInterfaceDescriptor} is totally isolate independent itself,
      this CL refactors the current design to avoid a copy of them per
      isolate, and instead shares them process-wide. Still, we need to free
      the allocated heap arrays when the last isolate dies to avoid leaks.
      This can probably be refactored later by statically initializing more
      and avoiding the heap allocations all together.
      
      This refactoring will also allow us to use {CallInterfaceDescriptor}s
      from wasm background compilation threads, which are not bound to any
      isolate.
      
      R=mstarzinger@chromium.org, titzer@chromium.org
      
      Bug: v8:6600
      Change-Id: If8625b89951eec8fa8986b49a5c166e874a72494
      Reviewed-on: https://chromium-review.googlesource.com/1100879
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Reviewed-by: 's avatarIgor Sheludko <ishell@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#53803}
      3cb376dc
  5. 04 Apr, 2018 1 commit
  6. 21 Feb, 2018 1 commit
  7. 09 Feb, 2018 1 commit
  8. 15 Nov, 2017 1 commit
  9. 01 Nov, 2017 1 commit
    • Leszek Swirski's avatar
      [compiler] Split compilation timer on caching decision · f571da95
      Leszek Swirski authored
      Rather than having a single script compilation timer, split it into
      multiple timers depending on the state of the (blink-owned) code cache
      and (v8-owned) complation cache. This is intended to replace both the
      script compilation time timer, and the compilation heuristic enum.
      
      Also keep track of why blink might not want us to produce (or consume) a
      code cache, and split the compilation timer on this as well.
      
      Note, there is currently no timer for streaming sources, so these won't
      show up in the histograms.
      
      Bug: chromium:582873
      Bug: chromium:769203
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: Ia32fff044f919e20e3cec73329e62e01e421b72a
      Reviewed-on: https://chromium-review.googlesource.com/746922
      Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49065}
      f571da95
  10. 13 Oct, 2017 1 commit
  11. 05 Oct, 2017 1 commit
  12. 29 Sep, 2017 2 commits
  13. 31 Aug, 2017 1 commit
    • Sathya Gunasekaran's avatar
      [Modules] Introduce ScriptOrModule and HostDefinedOptions · dbfe4a49
      Sathya Gunasekaran authored
      This patch introduces a new container type ScriptOrModule which
      provides the name and the host defined options of the script/module.
      
      This patch also introduces a new PrimitivesArray that can hold
      Primitive values, which the embedder can use to store metadata.
      
      The HostDefinedOptions is passed to V8 through the ScriptOrigin, and
      passed back to the embedder through HostImportModuleDynamically for
      module loading.
      
      Bug: v8:5785, v8:6658, v8:6683
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: I56c26fc9a680b273ac0a6691e5ad75f15b8dc80a
      Reviewed-on: https://chromium-review.googlesource.com/622158Reviewed-by: 's avatarAdam Klein <adamk@chromium.org>
      Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
      Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#47724}
      dbfe4a49
  14. 03 Aug, 2017 1 commit
  15. 21 Jul, 2017 1 commit
  16. 12 Jun, 2017 1 commit
  17. 27 Mar, 2017 1 commit
  18. 23 Feb, 2017 1 commit
  19. 10 Feb, 2017 1 commit
    • rmcilroy's avatar
      [Compiler] Enable use of seperate zones for parsing and compiling. · 1fc93f2e
      rmcilroy authored
      In order to allow parallel compilation of eager inner functions, we need to
      seperate the zone used for parsing (which will be shared between all the
      parallel compile jobs) and the zone used for compilation. This CL changes
      CompilationInfo to require a zone (which can be different from the zone in
      ParseInfo). We then seal the ParseInfo zone after parsing and analysis is done
      to prevent any further allocation in that zone, so that it can be shared
      (read-only) with the parallel compile jobs.
      
      BUG=v8:5203
      
      Review-Url: https://codereview.chromium.org/2645403002
      Cr-Commit-Position: refs/heads/master@{#43089}
      1fc93f2e
  20. 07 Feb, 2017 5 commits
  21. 24 Jan, 2017 1 commit
  22. 20 Jan, 2017 3 commits
  23. 19 Jan, 2017 1 commit
  24. 17 Oct, 2016 2 commits
  25. 07 Oct, 2016 2 commits
  26. 20 Sep, 2016 1 commit
  27. 31 Aug, 2016 1 commit
  28. 22 Aug, 2016 1 commit
  29. 09 Jun, 2016 1 commit
  30. 26 Apr, 2016 1 commit
  31. 08 Apr, 2016 1 commit