Add an --expose-wasm flag.

Add an --expose-wasm flag.

This adds a runtime flag that controls whether the WASM object is
exposed to JavaScript. While currently guarded by the V8_WASM build-time
flag, after landing in V8 the build-time flag will be removed, leaving
only this new runtime flag.

R=mstarzinger@chromium.org
BUG=

Committed: https://crrev.com/a29f81f603c05e080b54f8e1330575362c6579d5
Cr-Commit-Position: refs/heads/master@{#32657}

[Michael Starzinger, 2015-12-07 13:16:11]

LGTM.

[titzer, 2015-12-07 13:24:44]

The CQ bit was checked by titzer@chromium.org

[commit-bot: I haz the power, 2015-12-07 13:24:55]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1507623002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1507623002/1

[commit-bot: I haz the power, 2015-12-07 13:39:19]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-12-07 13:40:10]

Description was changed from

==========
Add an --expose-wasm flag.

This adds a runtime flag that controls whether the WASM object is
exposed to JavaScript. While currently guarded by the V8_WASM build-time
flag, after landing in V8 the build-time flag will be removed, leaving
only this new runtime flag.

R=mstarzinger@chromium.org
BUG=
==========

to

==========
Add an --expose-wasm flag.

This adds a runtime flag that controls whether the WASM object is
exposed to JavaScript. While currently guarded by the V8_WASM build-time
flag, after landing in V8 the build-time flag will be removed, leaving
only this new runtime flag.

R=mstarzinger@chromium.org
BUG=

Committed: https://crrev.com/a29f81f603c05e080b54f8e1330575362c6579d5
Cr-Commit-Position: refs/heads/master@{#32657}
==========

[commit-bot: I haz the power, 2015-12-07 13:40:11]

Patchset 1 (id:??) landed as
https://crrev.com/a29f81f603c05e080b54f8e1330575362c6579d5
Cr-Commit-Position: refs/heads/master@{#32657}