1. 10 Nov, 2016 1 commit
  2. 04 Nov, 2016 4 commits
  3. 03 Nov, 2016 1 commit
    • lpy's avatar
      [Tracing] Make TracingCategoryObserver v8 internal. · 2525b057
      lpy authored
      This patch removes TracingCategoryObserver API and moves the creation of
      observer inside platform initialization, by assuming that either
      Platform::AddTraceStateObserver is implemented correctly to add observer to
      tracing controller that implemented by embedders, or default tracing controller
      has already been set up and attached to platform before
      v8::V8::InitializePlatform is called.
      
      BUG=v8:5590
      
      Review-Url: https://codereview.chromium.org/2471583004
      Cr-Commit-Position: refs/heads/master@{#40739}
      2525b057
  4. 02 Nov, 2016 1 commit
  5. 01 Nov, 2016 1 commit
  6. 31 Oct, 2016 2 commits
  7. 28 Oct, 2016 2 commits
    • lpy's avatar
      [Tracing] Implement TracingCategoryObserver. · 6df8096a
      lpy authored
      This patch implements TracingCategoryObserver to set global flag when a V8
      specific category is enabled. Previously, we set a global flag each time when we
      encounter a top level trace event, and use it as a global check. With this
      patch, we can set a group of flags when tracing is enabled; besides, we make
      V8 tracing feature use V8 flags instead of defining its own flag in a messy way.
      
      With this patch, whatever V8 flag we want to imply in tracing, we define another
      integer flag, and the original V8 flag will set it to 0x01 when passing by
      commandline, tracing will set it to 0x10 when we start tracing and reset the bit
      when we stop tracing.
      
      Review-Url: https://codereview.chromium.org/2436273002
      Cr-Commit-Position: refs/heads/master@{#40659}
      6df8096a
    • jochen's avatar
      Add a native data property that replaces itself with a real data property · f0742150
      jochen authored
      This is useful for things that don't ever change, but we don't want to
      eagerly compute the result.
      
      Doing this from the embedder is difficult, using DefineOwnProperty would
      read the property to get the property descriptor, creating an endless
      recursion.
      
      R=verwaest@chromium.org,haraken@chromium.org
      BUG=
      
      Review-Url: https://codereview.chromium.org/2449783006
      Cr-Commit-Position: refs/heads/master@{#40648}
      f0742150
  8. 27 Oct, 2016 1 commit
  9. 22 Oct, 2016 1 commit
  10. 20 Oct, 2016 2 commits
  11. 13 Oct, 2016 2 commits
  12. 12 Oct, 2016 3 commits
  13. 11 Oct, 2016 2 commits
    • adamk's avatar
      [modules] Store Module metadata in per-Context EmbedderData · 9d2051fc
      adamk authored
      This is a re-land of https://codereview.chromium.org/2393303002/ with
      an additional call to DisposeModuleEmbedderData() added to fix lsan failures.
      
      Unifies the approaches used for storing the specifier -> module mapping
      and the module -> directory mapping, using std::unordered_maps for both
      and storing them per-Context.
      
      This requires adding a method to the v8::Module API to get a hash code
      for a Module, but allows slimming down the API in return: gone are
      SetEmbedderData/GetEmbedderData, along with the fourth argument
      to ResolveModuleCallback.
      
      Besides a simpler API, this allows d8 to get closer to the HTML loader,
      which requires each Realm to have a persistent module map (though this
      capability is not yet exercised by any tests).
      
      BUG=v8:1569
      TBR=neis@chromium.org,jochen@chromium.org
      
      Review-Url: https://codereview.chromium.org/2405313002
      Cr-Commit-Position: refs/heads/master@{#40186}
      9d2051fc
    • adamk's avatar
      Revert of [modules] Store Module metadata in per-Context EmbedderData... · 12779889
      adamk authored
      Revert of [modules] Store Module metadata in per-Context EmbedderData (patchset #7 id:120001 of https://codereview.chromium.org/2393303002/ )
      
      Reason for revert:
      Fails under LeakSanitizer on auto-roll fyi bot:
      
      https://build.chromium.org/p/client.v8.fyi/builders/Auto-roll%20-%20release%20process/builds/49447
      
      Original issue's description:
      > [modules] Store Module metadata in per-Context EmbedderData
      >
      > Unifies the approaches used for storing the specifier -> module mapping
      > and the module -> directory mapping, using std::unordered_maps for both
      > and storing them per-Context.
      >
      > This requires adding a method to the v8::Module API to get a hash code
      > for a Module, but allows slimming down the API in return: gone are
      > SetEmbedderData/GetEmbedderData, along with the fourth argument
      > to ResolveModuleCallback.
      >
      > Besides a simpler API, this allows d8 to get closer to the HTML loader,
      > which requires each Realm to have a persistent module map (though this
      > capability is not yet exercised by any tests).
      >
      > BUG=v8:1569
      >
      > Committed: https://crrev.com/9cf8fce74cf6e7afd6aea3f3545f6bb61572f277
      > Cr-Commit-Position: refs/heads/master@{#40133}
      
      TBR=jochen@chromium.org,neis@chromium.org
      # Skipping CQ checks because original CL landed less than 1 days ago.
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      BUG=v8:1569
      
      Review-Url: https://codereview.chromium.org/2406973003
      Cr-Commit-Position: refs/heads/master@{#40145}
      12779889
  14. 10 Oct, 2016 3 commits
    • adamk's avatar
      [modules] Store Module metadata in per-Context EmbedderData · 9cf8fce7
      adamk authored
      Unifies the approaches used for storing the specifier -> module mapping
      and the module -> directory mapping, using std::unordered_maps for both
      and storing them per-Context.
      
      This requires adding a method to the v8::Module API to get a hash code
      for a Module, but allows slimming down the API in return: gone are
      SetEmbedderData/GetEmbedderData, along with the fourth argument
      to ResolveModuleCallback.
      
      Besides a simpler API, this allows d8 to get closer to the HTML loader,
      which requires each Realm to have a persistent module map (though this
      capability is not yet exercised by any tests).
      
      BUG=v8:1569
      
      Review-Url: https://codereview.chromium.org/2393303002
      Cr-Commit-Position: refs/heads/master@{#40133}
      9cf8fce7
    • jochen's avatar
      Turn libplatform into a component · c59cf8cd
      jochen authored
      BUG=v8:5412
      R=jgruber@chromium.org,machenbach@chromium.org
      CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_compile_dbg_ng;master.tryserver.chromium.android:android_clang_dbg_recipe
      
      Review-Url: https://codereview.chromium.org/2372983003
      Cr-Commit-Position: refs/heads/master@{#40111}
      c59cf8cd
    • mtrofin's avatar
      [wasm] Avoid copying when deserializing wasm · cc02e743
      mtrofin authored
      Updated the deserialization API to avoid copying uncompiled
      bytes.
      
      BUG=
      
      Review-Url: https://codereview.chromium.org/2404673002
      Cr-Commit-Position: refs/heads/master@{#40108}
      cc02e743
  15. 07 Oct, 2016 1 commit
  16. 06 Oct, 2016 3 commits
    • mtrofin's avatar
      [wasm] Support recompilation if deserialization fails. · 917ef616
      mtrofin authored
      One step closer to the informally-agreed upon specification
      that structured cloning will always succeed, meaning, if
      we fail to deserialize (e.g. because version mismatch in
      serialized format and v8 version), we recompile.
      
      As part of this work, the deserializer will need to become
      more resilient to invalid input data, and fail graciously
      rather than CHECK-ing. This CL addresses some of that,
      sufficient to unblock the current serialization tests.
      Subsequent CLs will add more testing and the appropriate
      fixes.
      
      BUG=639090
      
      Review-Url: https://codereview.chromium.org/2395793003
      Cr-Commit-Position: refs/heads/master@{#40058}
      917ef616
    • alph's avatar
      [profiler] Tracing-based CPU profiler. · 4b575dfc
      alph authored
      A new V8 API object v8::TracingCpuProfiler is introduced.
      Client can create it on an isolate to enable JS CPU profiles collected
      during tracing session.
      
      Once the v8.cpu_profile2 tracing category is enabled the profiler emits
      CpuProfile and CpuProfileChunk events with the profile data.
      
      BUG=chromium:406277
      
      Review-Url: https://codereview.chromium.org/2396733002
      Cr-Commit-Position: refs/heads/master@{#40054}
      4b575dfc
    • hablich's avatar
      Update version to 5.6 · eeaa2398
      hablich authored
      TBR=machenbach@chromium.org
      NOTREECHECKS=true
      NOTRY=true
      
      Review-Url: https://codereview.chromium.org/2397153002
      Cr-Commit-Position: refs/heads/master@{#40037}
      eeaa2398
  17. 04 Oct, 2016 1 commit
  18. 29 Sep, 2016 2 commits
  19. 28 Sep, 2016 2 commits
  20. 27 Sep, 2016 4 commits
  21. 26 Sep, 2016 1 commit