[wasm] Rename _WASMEXP_ object to Wasm.

[wasm] Rename _WASMEXP_ object to Wasm.

R=ahaas@chromium.org,binji@chromium.org
BUG=

Committed: https://crrev.com/5c1c98e8295012bbf2cabbf2fcb18f2ac2a7848b
Cr-Commit-Position: refs/heads/master@{#34587}

[ahaas, 2016-03-08 13:47:00]

lgtm

[titzer, 2016-03-08 14:45:21]

The CQ bit was checked by titzer@chromium.org

[commit-bot: I haz the power, 2016-03-08 14:45:31]

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

[commit-bot: I haz the power, 2016-03-08 14:47:04]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-03-08 14:48:34]

Description was changed from

==========
[wasm] Rename _WASMEXP_ object to Wasm.

R=ahaas@chromium.org,binji@chromium.org
BUG=
==========

to

==========
[wasm] Rename _WASMEXP_ object to Wasm.

R=ahaas@chromium.org,binji@chromium.org
BUG=

Committed: https://crrev.com/5c1c98e8295012bbf2cabbf2fcb18f2ac2a7848b
Cr-Commit-Position: refs/heads/master@{#34587}
==========

[commit-bot: I haz the power, 2016-03-08 14:48:35]

Patchset 2 (id:??) landed as
https://crrev.com/5c1c98e8295012bbf2cabbf2fcb18f2ac2a7848b
Cr-Commit-Position: refs/heads/master@{#34587}

[Derek Schuff, 2016-03-08 16:46:57]

On 2016/03/08 14:48:35, commit-bot: I haz the power wrote:
> Patchset 2 (id:??) landed as
> https://crrev.com/5c1c98e8295012bbf2cabbf2fcb18f2ac2a7848b
> Cr-Commit-Position: refs/heads/master@{#34587}

So, one problem with landing this now is that now we have no way to determine in
the Binaryen code whether we need to flatten the imports object. Before You
could check whether _WASMEXP_ or Wasm was an object. Is there some other way I
can tell I'm in V8 instead of SM?

[Derek Schuff, 2016-03-08 16:47:00]

On 2016/03/08 14:48:35, commit-bot: I haz the power wrote:
> Patchset 2 (id:??) landed as
> https://crrev.com/5c1c98e8295012bbf2cabbf2fcb18f2ac2a7848b
> Cr-Commit-Position: refs/heads/master@{#34587}

So, one problem with landing this now is that now we have no way to determine in
the Binaryen code whether we need to flatten the imports object. Before You
could check whether _WASMEXP_ or Wasm was an object. Is there some other way I
can tell I'm in V8 instead of SM?

[titzer, 2016-03-08 16:57:50]

On 2016/03/08 16:47:00, Derek Schuff wrote:
> On 2016/03/08 14:48:35, commit-bot: I haz the power wrote:
> > Patchset 2 (id:??) landed as
> > https://crrev.com/5c1c98e8295012bbf2cabbf2fcb18f2ac2a7848b
> > Cr-Commit-Position: refs/heads/master@{#34587}
> 
> So, one problem with landing this now is that now we have no way to determine
in
> the Binaryen code whether we need to flatten the imports object. Before You
> could check whether _WASMEXP_ or Wasm was an object. Is there some other way I
> can tell I'm in V8 instead of SM?

I'm in the middle of implementing the two-level imports so that should just go
away.