[wasm] Always provide a wasm instance object at runtime

[wasm] Always provide a wasm instance object at runtime

When executing wasm code for testing, we did not create a
WasmInstanceObject and link it to the generated code. This required
some special handling at runtime (mainly for stack trace generation).
This CL always provides the WasmInstanceObject, such that e.g. function
names can be resolved the usual way.
The module bytes referenced by the WasmCompiledModule linked with the
WasmInstanceObject do not hold a valid wasm module yet. Instead, we
just add the bytes we need, and make the objects in WasmModule point to
those bytes (currently only used for function names). Those bytes will
not be parsed at runtime anyway.

R=titzer@chromium.org
CC=jgruber@chromium.org
BUG=v8:5620
Review-Url: https://codereview.chromium.org/2551053002
Cr-Commit-Position: refs/heads/master@{#41809}
Committed: https://chromium.googlesource.com/v8/v8/+/21a85c4a03833b3fe70bfcd8ab414b42750475e9

[Clemens Hammacher, 2016-12-05 08:57:21]

The CQ bit was checked by clemensh@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-05 08:57:32]

Dry run: 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, 2016-12-05 09:18:59]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-05 09:18:59]

Dry run: Try jobs failed on following builders:
  v8_linux_dbg_ng on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_dbg_ng/builds/17337)
  v8_linux_dbg_ng_triggered on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_dbg_ng_triggered/b...)

[Clemens Hammacher, 2016-12-05 11:44:19]

The CQ bit was checked by clemensh@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-05 11:44:26]

Dry run: 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, 2016-12-05 12:11:23]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-05 12:11:24]

Dry run: This issue passed the CQ dry run.

[jgruber, 2016-12-05 12:22:06]

Awesome, thanks!

[Clemens Hammacher, 2016-12-19 14:30:39]

The CQ bit was checked by clemensh@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-19 14:30:48]

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

[titzer, 2016-12-19 14:39:59]

On 2016/12/05 12:22:06, jgruber wrote:
> Awesome, thanks!

lgtm

[commit-bot: I haz the power, 2016-12-19 15:00:50]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-19 15:00:51]

Dry run: This issue passed the CQ dry run.

[Clemens Hammacher, 2016-12-19 15:01:37]

The CQ bit was checked by clemensh@chromium.org

[commit-bot: I haz the power, 2016-12-19 15:01:39]

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, 2016-12-19 15:03:13]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1482159697087950,
"parent_rev": "34d2402a0b5851e29e71e95fd4aa7b888d751f47", "commit_rev":
"21a85c4a03833b3fe70bfcd8ab414b42750475e9"}

[commit-bot: I haz the power, 2016-12-19 15:03:24]

Description was changed from

==========
[wasm] Always provide a wasm instance object at runtime

When executing wasm code for testing, we did not create a
WasmInstanceObject and link it to the generated code. This required
some special handling at runtime (mainly for stack trace generation).
This CL always provides the WasmInstanceObject, such that e.g. function
names can be resolved the usual way.
The module bytes referenced by the WasmCompiledModule linked with the
WasmInstanceObject do not hold a valid wasm module yet. Instead, we
just add the bytes we need, and make the objects in WasmModule point to
those bytes (currently only used for function names). Those bytes will
not be parsed at runtime anyway.

R=titzer@chromium.org
CC=jgruber@chromium.org
BUG=v8:5620
==========

to

==========
[wasm] Always provide a wasm instance object at runtime

When executing wasm code for testing, we did not create a
WasmInstanceObject and link it to the generated code. This required
some special handling at runtime (mainly for stack trace generation).
This CL always provides the WasmInstanceObject, such that e.g. function
names can be resolved the usual way.
The module bytes referenced by the WasmCompiledModule linked with the
WasmInstanceObject do not hold a valid wasm module yet. Instead, we
just add the bytes we need, and make the objects in WasmModule point to
those bytes (currently only used for function names). Those bytes will
not be parsed at runtime anyway.

R=titzer@chromium.org
CC=jgruber@chromium.org
BUG=v8:5620

Review-Url: https://codereview.chromium.org/2551053002
Cr-Commit-Position: refs/heads/master@{#41809}
Committed:
https://chromium.googlesource.com/v8/v8/+/21a85c4a03833b3fe70bfcd8ab414b42750...
==========

[commit-bot: I haz the power, 2016-12-19 15:03:25]

Committed patchset #3 (id:40001) as
https://chromium.googlesource.com/v8/v8/+/21a85c4a03833b3fe70bfcd8ab414b42750...