[wasm] Also unwrap exported debugged functions

[wasm] Also unwrap exported debugged functions

The previous fix (http://crrev.com/2720813002) was problematic for
functions containing i64 parameters or returns. Those would throw a
TypeError when called via WASM_TO_JS and JS_TO_WASM.

Instead, we now unwrap the WASM_INTERPRETER_ENTRY function and call it
directly. This removes the option to later redirect back to the
original wasm function, but this functionality is not needed currently.

Plus drive-by fix to put functions in anonymous namespace in
wasm-compiler.cc.

R=ahaas@chromium.org, titzer@chromium.org
BUG=v8:5971, v8:5822
Review-Url: https://codereview.chromium.org/2725333002
Cr-Commit-Position: refs/heads/master@{#43603}
Committed: https://chromium.googlesource.com/v8/v8/+/66964e68e44afe6dcbf1e7495ae08e8fc7a6964c

[Clemens Hammacher, 2017-03-03 14:59:35]

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

[commit-bot: I haz the power, 2017-03-03 14:59:42]

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, 2017-03-03 15:24:42]

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

[commit-bot: I haz the power, 2017-03-03 15:24:45]

Dry run: This issue passed the CQ dry run.

[Clemens Hammacher, 2017-03-03 15:29:33]

Andreas spotted this problem in the previous fix.

[titzer, 2017-03-06 07:16:06]

lgtm

[Clemens Hammacher, 2017-03-06 09:25:33]

The CQ bit was checked by clemensh@chromium.org

[commit-bot: I haz the power, 2017-03-06 09:25:38]

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-06 09:53:33]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1488792333097910, "parent_rev":
"437dece4d9f06d12d7a8e38ee07e820c07533f9c", "commit_rev":
"66964e68e44afe6dcbf1e7495ae08e8fc7a6964c"}

[commit-bot: I haz the power, 2017-03-06 09:53:38]

Description was changed from

==========
[wasm] Also unwrap exported debugged functions

The previous fix (http://crrev.com/2720813002) was problematic for
functions containing i64 parameters or returns. Those would throw a
TypeError when called via WASM_TO_JS and JS_TO_WASM.

Instead, we now unwrap the WASM_INTERPRETER_ENTRY function and call it
directly. This removes the option to later redirect back to the
original wasm function, but this functionality is not needed currently.

Plus drive-by fix to put functions in anonymous namespace in
wasm-compiler.cc.

R=ahaas@chromium.org, titzer@chromium.org
BUG=v8:5971, v8:5822
==========

to

==========
[wasm] Also unwrap exported debugged functions

The previous fix (http://crrev.com/2720813002) was problematic for
functions containing i64 parameters or returns. Those would throw a
TypeError when called via WASM_TO_JS and JS_TO_WASM.

Instead, we now unwrap the WASM_INTERPRETER_ENTRY function and call it
directly. This removes the option to later redirect back to the
original wasm function, but this functionality is not needed currently.

Plus drive-by fix to put functions in anonymous namespace in
wasm-compiler.cc.

R=ahaas@chromium.org, titzer@chromium.org
BUG=v8:5971, v8:5822

Review-Url: https://codereview.chromium.org/2725333002
Cr-Commit-Position: refs/heads/master@{#43603}
Committed:
https://chromium.googlesource.com/v8/v8/+/66964e68e44afe6dcbf1e7495ae08e8fc7a...
==========

[commit-bot: I haz the power, 2017-03-06 09:53:38]

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