Reland of [wasm] Transferrable modules

Reland of [wasm] Transferrable modules (patchset #1 id:1 of https://codereview.chromium.org/2762163002/ )

Reason for revert:
Temporarily disabled tests on chromium side (https://codereview.chromium.org/2764933002)

Original issue's description:
> Revert of [wasm] Transferrable modules (patchset #13 id:280001 of https://codereview.chromium.org/2748473004/ )
> 
> Reason for revert:
> Breaks layout tests:
> https://build.chromium.org/p/client.v8.fyi/builders/V8-Blink%20Linux%2064/builds/14312
> 
> See https://github.com/v8/v8/wiki/Blink-layout-tests
> 
> Original issue's description:
> > [wasm] Transferrable modules
> > 
> > We want to restrict structured cloning in Chrome to:
> > - postMessage senders and receivers that are co-located 
> > in the same process
> > - indexedDB (just https).
> > 
> > For context, on the Chrome side, we will achieve the postMessage part 
> > by using a mechanism similar to transferrables: the 
> > SerializedScriptValue will have a list of wasm modules, separate from 
> > the serialized data stream; and this list won't be copied cross 
> > process boundaries. The IDB part is achieved by explicitly opting in
> > reading/writing to the serialization stream. To block attack vectors 
> > in IPC cases, the default for deserialization will be to expect data 
> > in the wasm transfers list.
> > 
> > This change is the V8 side necessary to enabling this design. We 
> > introduce TransferrableModule, an opaque datatype exposed to the
> > embedder. Internally, TransferrableModules are just serialized data,
> > because we don't have a better mechanism, at the moment, for
> > de-contextualizing/re-contextualizing wasm modules (wrt Isolate and 
> > Context).
> > 
> > The chrome defaults will be implemented in the 
> > serialization/deserialization delegates on that side. For the v8 side 
> > of things, in the absence of a serialization delegate, the V8
> > serializer will write to serialization stream. In the absence of a 
> > deserialization delegate, the deserializer won't work. This asymmetry
> > is intentional - it communicates to the embedder the need to make a 
> > policy decision, otherwise wasm serialization/deserialization won't 
> > work "out of the box".
> > 
> > BUG=v8:6079
> > 
> > Review-Url: https://codereview.chromium.org/2748473004
> > Cr-Commit-Position: refs/heads/master@{#43955}
> > Committed: https://chromium.googlesource.com/v8/v8/+/99743ad460ea5b9795ba9d70a074e75d7362a3d1
> 
> TBR=jbroman@chromium.org,bradnelson@chromium.org,mtrofin@chromium.org
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=v8:6079
> 
> Review-Url: https://codereview.chromium.org/2762163002
> Cr-Commit-Position: refs/heads/master@{#43981}
> Committed: https://chromium.googlesource.com/v8/v8/+/e538b70e1a45289dfe0fa9789563f023a5e9c22b

TBR=jbroman@chromium.org,bradnelson@chromium.org,machenbach@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=v8:6079
Review-Url: https://codereview.chromium.org/2762273002
Cr-Commit-Position: refs/heads/master@{#43994}
Committed: https://chromium.googlesource.com/v8/v8/+/9dfa46395aff0d84a17fccb4b4cceb250c0e1fc9

[Mircea Trofin, 2017-03-21 17:47:47]

The CQ bit was checked by mtrofin@chromium.org

[Mircea Trofin, 2017-03-21 17:47:47]

Created Reland of [wasm] Transferrable modules

[commit-bot: I haz the power, 2017-03-21 17:47:58]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-21 17:48:06]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1490118467179690, "parent_rev":
"154369bb5af9b2e1ff6094df52b94f56219a402c", "commit_rev":
"9dfa46395aff0d84a17fccb4b4cceb250c0e1fc9"}

[commit-bot: I haz the power, 2017-03-21 17:48:12]

Description was changed from

==========
Reland of [wasm] Transferrable modules (patchset #1 id:1 of
https://codereview.chromium.org/2762163002/ )

Reason for revert:
Temporarily disabled tests on chromium side
(https://codereview.chromium.org/2764933002)

Original issue's description:
> Revert of [wasm] Transferrable modules (patchset #13 id:280001 of
https://codereview.chromium.org/2748473004/ )
> 
> Reason for revert:
> Breaks layout tests:
>
https://build.chromium.org/p/client.v8.fyi/builders/V8-Blink%20Linux%2064/bui...
> 
> See https://github.com/v8/v8/wiki/Blink-layout-tests
> 
> Original issue's description:
> > [wasm] Transferrable modules
> > 
> > We want to restrict structured cloning in Chrome to:
> > - postMessage senders and receivers that are co-located 
> > in the same process
> > - indexedDB (just https).
> > 
> > For context, on the Chrome side, we will achieve the postMessage part 
> > by using a mechanism similar to transferrables: the 
> > SerializedScriptValue will have a list of wasm modules, separate from 
> > the serialized data stream; and this list won't be copied cross 
> > process boundaries. The IDB part is achieved by explicitly opting in
> > reading/writing to the serialization stream. To block attack vectors 
> > in IPC cases, the default for deserialization will be to expect data 
> > in the wasm transfers list.
> > 
> > This change is the V8 side necessary to enabling this design. We 
> > introduce TransferrableModule, an opaque datatype exposed to the
> > embedder. Internally, TransferrableModules are just serialized data,
> > because we don't have a better mechanism, at the moment, for
> > de-contextualizing/re-contextualizing wasm modules (wrt Isolate and 
> > Context).
> > 
> > The chrome defaults will be implemented in the 
> > serialization/deserialization delegates on that side. For the v8 side 
> > of things, in the absence of a serialization delegate, the V8
> > serializer will write to serialization stream. In the absence of a 
> > deserialization delegate, the deserializer won't work. This asymmetry
> > is intentional - it communicates to the embedder the need to make a 
> > policy decision, otherwise wasm serialization/deserialization won't 
> > work "out of the box".
> > 
> > BUG=v8:6079
> > 
> > Review-Url: https://codereview.chromium.org/2748473004
> > Cr-Commit-Position: refs/heads/master@{#43955}
> > Committed:
https://chromium.googlesource.com/v8/v8/+/99743ad460ea5b9795ba9d70a074e75d736...
> 
> TBR=jbroman@chromium.org,bradnelson@chromium.org,mtrofin@chromium.org
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=v8:6079
> 
> Review-Url: https://codereview.chromium.org/2762163002
> Cr-Commit-Position: refs/heads/master@{#43981}
> Committed:
https://chromium.googlesource.com/v8/v8/+/e538b70e1a45289dfe0fa9789563f023a5e...

TBR=jbroman@chromium.org,bradnelson@chromium.org,machenbach@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=v8:6079
==========

to

==========
Reland of [wasm] Transferrable modules (patchset #1 id:1 of
https://codereview.chromium.org/2762163002/ )

Reason for revert:
Temporarily disabled tests on chromium side
(https://codereview.chromium.org/2764933002)

Original issue's description:
> Revert of [wasm] Transferrable modules (patchset #13 id:280001 of
https://codereview.chromium.org/2748473004/ )
> 
> Reason for revert:
> Breaks layout tests:
>
https://build.chromium.org/p/client.v8.fyi/builders/V8-Blink%20Linux%2064/bui...
> 
> See https://github.com/v8/v8/wiki/Blink-layout-tests
> 
> Original issue's description:
> > [wasm] Transferrable modules
> > 
> > We want to restrict structured cloning in Chrome to:
> > - postMessage senders and receivers that are co-located 
> > in the same process
> > - indexedDB (just https).
> > 
> > For context, on the Chrome side, we will achieve the postMessage part 
> > by using a mechanism similar to transferrables: the 
> > SerializedScriptValue will have a list of wasm modules, separate from 
> > the serialized data stream; and this list won't be copied cross 
> > process boundaries. The IDB part is achieved by explicitly opting in
> > reading/writing to the serialization stream. To block attack vectors 
> > in IPC cases, the default for deserialization will be to expect data 
> > in the wasm transfers list.
> > 
> > This change is the V8 side necessary to enabling this design. We 
> > introduce TransferrableModule, an opaque datatype exposed to the
> > embedder. Internally, TransferrableModules are just serialized data,
> > because we don't have a better mechanism, at the moment, for
> > de-contextualizing/re-contextualizing wasm modules (wrt Isolate and 
> > Context).
> > 
> > The chrome defaults will be implemented in the 
> > serialization/deserialization delegates on that side. For the v8 side 
> > of things, in the absence of a serialization delegate, the V8
> > serializer will write to serialization stream. In the absence of a 
> > deserialization delegate, the deserializer won't work. This asymmetry
> > is intentional - it communicates to the embedder the need to make a 
> > policy decision, otherwise wasm serialization/deserialization won't 
> > work "out of the box".
> > 
> > BUG=v8:6079
> > 
> > Review-Url: https://codereview.chromium.org/2748473004
> > Cr-Commit-Position: refs/heads/master@{#43955}
> > Committed:
https://chromium.googlesource.com/v8/v8/+/99743ad460ea5b9795ba9d70a074e75d736...
> 
> TBR=jbroman@chromium.org,bradnelson@chromium.org,mtrofin@chromium.org
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=v8:6079
> 
> Review-Url: https://codereview.chromium.org/2762163002
> Cr-Commit-Position: refs/heads/master@{#43981}
> Committed:
https://chromium.googlesource.com/v8/v8/+/e538b70e1a45289dfe0fa9789563f023a5e...

TBR=jbroman@chromium.org,bradnelson@chromium.org,machenbach@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=v8:6079

Review-Url: https://codereview.chromium.org/2762273002
Cr-Commit-Position: refs/heads/master@{#43994}
Committed:
https://chromium.googlesource.com/v8/v8/+/9dfa46395aff0d84a17fccb4b4cceb250c0...
==========

[commit-bot: I haz the power, 2017-03-21 17:48:15]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/v8/v8/+/9dfa46395aff0d84a17fccb4b4cceb250c0...