1. 11 Dec, 2018 1 commit
  2. 05 Dec, 2018 1 commit
  3. 21 Jun, 2018 1 commit
    • Clemens Hammacher's avatar
      [api] Properly define BufferReference instead of CallerOwnedBuffer · e90af2c7
      Clemens Hammacher authored
      The name {CallerOwnedBuffer} does not make sense in all situations,
      especially if such an object is returned instead of being passed as
      argument.
      I am working on moving the wasm wire bytes off the JS heap, and hence
      will return unowned references via the API. To prepare this change, I
      deprecate the existing {CallerOwnedBuffer} and introduce a new
      {BufferReference} struct with proper field names.
      
      R=titzer@chromium.org, adamk@chromium.org
      
      Bug: v8:7868
      Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng
      Change-Id: Ic8953951447038a831b15a336a52a199bfbeafd5
      Reviewed-on: https://chromium-review.googlesource.com/1108207Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Reviewed-by: 's avatarBen Titzer <titzer@chromium.org>
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#53929}
      e90af2c7
  4. 09 Nov, 2017 1 commit
    • Karl Schimpf's avatar
      Add capability to handle CSP 'wasm-eval' in V8 · 1719ecb9
      Karl Schimpf authored
      Like CSP flag 'unsafe-eval', which communicates if both JS source
      files and WASM binary files may be compiled, this CL adds a similar
      flag for the compilation of WASM binary files.
      
      That is, a WASM binary file will be compiled only if the new flag is
      defined, or the flag for 'unsafe-eval' allows it. These flags are
      implemented as callback functions on the isolate. The callbacks get a
      (CSP) context, and a string, and returns the corresponding value of
      the flag.
      
      Both callbacks are initialized with the nullptr, and is used to
      communicate that no CSP policy is defined. This allows this concept to
      work, independent of it running in Chrome.
      
      It also does a small clean up in api.cc to use macro CALLER_SETTERS,
      instead of explicit code when appropriate.
      
      Bug: v8:7041
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: Idb3356574ae2a298057e6b7bccbd3492831952ae
      Reviewed-on: https://chromium-review.googlesource.com/759162Reviewed-by: 's avatarBill Budge <bbudge@chromium.org>
      Reviewed-by: 's avatarEric Holk <eholk@chromium.org>
      Commit-Queue: Karl Schimpf <kschimpf@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49243}
      1719ecb9